docs(falkordb): clarify relations-as-nodes and per-call projection reads - #40
Merged
Merged
Conversation
Two accuracy fixes to the FalkorDB guide following the v1.1 merge: - The "query with Cypher" use case implied native graph-algorithm traversal, but relations are stored as AGRelation nodes (not native edges) to preserve dangling-relation semantics. Clarify that Cypher queries match on source/target properties and that edge-traversal algorithms don't apply directly. - Note that Graph's filters, neighborhood walks, and where evaluation run in Python over all_objects()/all_relations(), so each call reads the whole projection from FalkorDB rather than pushing a query down. Sets expectations: best for small-to-medium projections and inspection. Docs only; no code or behavior changes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NakhiG72ivaQT7su157hKj
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two small accuracy fixes to the FalkorDB guide, following the #39 merge. Docs only — no code or behavior changes.
What & why
Relations-as-nodes clarification. The "Query current state with Cypher" use case implied native graph-algorithm traversal. But
FalkorDBGraphStorestores relations asAGRelationnodes, not native edges (intentionally — to preserve the in-memory store's dangling-relation semantics). The guide now says to matchAGRelationnodes by theirsource/targetproperties and notes that native edge-traversal algorithms don't apply directly.Per-call projection reads.
Graph's filters,neighborhood(), andwhereevaluation run in Python overall_objects()/all_relations(), so each call fetches and decodes the whole projection from FalkorDB rather than pushing the query down as Cypher. Added a note to the data-model section so readers know this is best for small-to-medium live projections and Cypher-side inspection, not large pushed-down traversals.Both points reflect the actual implementation merged in #39; this just sets reader expectations accurately.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NakhiG72ivaQT7su157hKj
Generated by Claude Code