-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incorrect result for composite index ["name", "age"]
, filtering tag.name == "foo" OR tag.age > 41
#3603
Comments
wey-gu
changed the title
incorrect result for composite index
incorrect result for composite index Dec 30, 2021
["name", "age"]
, filtering tag.name == "foo" OR tag.age > 41["name", "age"]
, filtering tag.name == "foo" OR tag.age > 41
Would you please paste the execution plan for us? |
Here it is:
|
Merged
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I understand it correctly, with composite index
["name", "age"]
, tag.name == "foo" OR tag.age > 41 should end up no index found due to name's length is not fixed(to enable left scan of "age" field).While in the build(not the one before merge, but close to) from multi-match PR, the result is incorrect:
Your Environments (required)
How To Reproduce(required)
Steps to reproduce the behavior:
Expected behavior
Additional context
Found this when I was trying to answer https://discuss.nebula-graph.com.cn/t/topic/7065
The text was updated successfully, but these errors were encountered: