Skip to content

fix(gfql): return empty temporal traversal results - #2166

Merged
lmeyerov merged 3 commits into
masterfrom
fix/gfql-no-match-temporal-traversal-2161
Oct 9, 2026
Merged

lmeyerov merged 3 commits into
masterfrom
fix/gfql-no-match-temporal-traversal-2161

Conversation

@lmeyerov

@lmeyerov lmeyerov commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Valid no-match timestamp edge predicates return empty results through native and Cypher Polars traversal. Empty eager wavefronts use the existing temporal parser and a native Polars literal; malformed-value behavior, precision, schema and input ownership are preserved.

Closes #2161.

Validation: two source review waves plus two test-correction reviews; 888 focused CPU tests passed; changed-module types and Ruff passed. RAPIDS 26.02 passed 87 focused cases; 25.02 passed 69 with 18 configured-executor capability skips. The bounded matched performance control passed all 12 cells (current/baseline 0.997–1.003×; maximum A/A drift 0.52%). Thresholds and failed evidence are retained.

Merged as b3575b494aa94625f9a2df47ddd0a2a77d2f2714; #2161 is closed. Final-head CI and Read the Docs passed, and the merged tree matches the validated head. The final 0.60.0 revision 5bb1217856bc4161e7aa4ff5ff3ba08943c78069 also passed master CI and latest docs. Runtime and tests remain byte-identical to the accepted GPU source.

@lmeyerov
lmeyerov marked this pull request as ready for review October 9, 2026 06:32
@lmeyerov
lmeyerov merged commit b3575b4 into master Oct 9, 2026
72 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GFQL Polars: no-match timestamp edge traversal raises with indexes off

1 participant