fix(gfql): index bounded range hops - #1839
Merged
Merged
Conversation
lmeyerov
marked this pull request as ready for review
July 31, 2026 03:21
lmeyerov
force-pushed
the
fix/gfql-index-bounded-range-hop
branch
from
July 31, 2026 07:03
00e0d53 to
93eff17
Compare
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
1 participant
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.
Fixes direct seeded hops expressed as hops=None, min_hops=1, max_hops=N: the index planner now validates the effective max depth rather than declining before the existing depth-union traversal runs.\n\nAdds forced-index vs scan parity and index-engagement coverage across available engines.\n\nValidation: DGX official image with --gpus all, full GFQL index module (170 passed); local lint and pinned mypy 2.3.0.\n\nThis is a correctness PR, not a performance claim; Cypher chain label/reverse-pass semantics remain intentionally scan-routed.