-
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
composite index OR filter not included in columnHints #4847
Comments
That's indeed a problem, and fixing it may require refactoring some old code.. |
This is not a result error, just performance degradation. To fix it, we may need to do a major refactor to the index selection module, so could we move it to 3.5? @xtcyclist @yixinglu |
Agree with you. |
I'm closing this issue and removing it from the 3.5 milestone due to resource constraints. We welcome anyone from the community to address this issue lateron. |
Introduction
If we do OR conditions for single column indexscan, the filter could be pushdown as optimal.
While it seems in the composite index case, it's full scan.
Contents
Related work
In Lookup, it's working as expected:
The text was updated successfully, but these errors were encountered: