-
Notifications
You must be signed in to change notification settings - Fork 99
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
Cartesian product + Index cause wrong result #1648
Comments
Hello @Aurora-yzj, and thank you for opening this issue! Someone from the team will get back to you. |
I am pausing the issue due to no progress. This issue only happens in combination of CartesianProduct + right_operator=ScanAllByLabelPropertyRange (which means it only fails for label-property indexes). I've tried multiple equivalent queries but only this one uses CartesianProduct. Also I find it weird that no combination other than the given one produced CartesianProduct using ScanAllByLabelPropertyRange, maybe it is a problem with planner but I don't know enough about it at the moment. |
@Aurora-yzj If that is a blocker for you, try running memgraph with --cartesian-product-enabled=false, I'm pretty sure the issue won't happen then since this is a problem with cartesian product but your queries memory and speed might be impacted due to not using cartesian. |
Memgraph version
2.13.0
Environment
Operating system: Ubuntu 22.04
Architecture: AMD64
Connect method: any connect method
Driver: any driver
With docker
Describe the bug
Memgraph outputs an empty query result when using an index.
To Reproduce
Steps to reproduce the behavior:
This query should return some results but it returns an empty result:
If we don't create the index in Step 1 (delete the first line in Step 1), then this query will output the result normally:
Expected behavior
The query should return normal results with the index created.
Besides, while minimizing the test case, I also found that the UNWIND clause in this query is crucial in reproducing this issue. Hope this will help you locate the root cause. Thank you!
Verification Environment
The text was updated successfully, but these errors were encountered: