Conversation
ANY graph node patterns bind labels like User and City to the internal _nodes table, where user-defined properties are stored inside the JSON data column. Scan planning was still trying to read dynamic properties such as name as physical columns, so MATCH ... RETURN u.name either failed during mapping or produced no useful result after CREATE. Teach ScanNodeTable mapping to scan the data column for missing physical properties on ANY graph tables, and extend ColumnCaster to extract the requested JSON key into the projected result vector. This keeps normal physical-column scans unchanged while allowing dynamic properties to be returned from ANY graphs. Add regression coverage for creating a User-[:LivesIn]->City pattern and returning u.name and c.name.
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.
ANY graph node patterns bind labels like User and City to the internal _nodes table, where user-defined properties are stored inside the JSON data column. Scan planning was still trying to read dynamic properties such as name as physical columns, so MATCH ... RETURN u.name either failed during mapping or produced no useful result after CREATE.
Teach ScanNodeTable mapping to scan the data column for missing physical properties on ANY graph tables, and extend ColumnCaster to extract the requested JSON key into the projected result vector. This keeps normal physical-column scans unchanged while allowing dynamic properties to be returned from ANY graphs.
Add regression coverage for creating a User-[:LivesIn]->City pattern and returning u.name and c.name.