Support variable when seeking by id in match clause #5486
Merged
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.
What type of PR is this?
What problem(s) does this PR solve?
Issue(s) number:
#5509
Description:
The following query will execute full index scan even though the filter in where clause is from some specified vid list. it's very slow for these cases since nebula could not find a reasonable start point for path pattern.
How do you solve it?
I add a new start point seeker in match planner to generate a argument plan node referencing the input data from other clause. this argument plan node can avoid to scan all index or vertices/edges.
In this PR, I restrict the usage of the seeker for the filter related to node and exclude the case that some variable is from current match path pattern, such as:
The index selection for variable will be supported in next pr.
Special notes for your reviewer, ex. impact of this fix, design document, etc:
Checklist:
Tests:
Affects:
Release notes:
Please confirm whether to be reflected in release notes and how to describe: