[PROTOTYPE] Filter Conditions on Paths #20159
Draft
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.
Scope & Purpose
This is a prototype PR, not to be merged as is.
The goal of this work is to detect conditions that have to hold for all vertices/edges on paths, for instance as in the following query
and optimize path search by abandoning all searches that would involve vertices/edges that don't satisfy this global condition.
This involves multiple things to happen:
FILTER
statements that access the path variable of a path enumeration using an expansionAt the moment all these steps happen in this one PR in various levels of completion.