-
Notifications
You must be signed in to change notification settings - Fork 25.3k
fix Optimization: Use Lucene's TwoPhaseIterator for quick filtering t… #129893
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
base: 7.17
Are you sure you want to change the base?
Conversation
…o improve query efficiency
❌ Author of the following commits did not sign a Contributor Agreement: Please, read and sign the above mentioned agreement if you want to contribute to this project |
Using Lucene's Two Phase Query submission to optimize match queries |
1 similar comment
Using Lucene's Two Phase Query submission to optimize match queries |
…o improve query efficiency
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
Heya @csywxr , thanks for opening this PR! Could you please share more context on what originated this, what problems it solves, and also why it was opened against the 7.17 branch instead of main? Thanks! |
Hello Javanna |
Hello Javanna |
Thanks for getting back to me. Do you have benchmarks results of the impact? Asking because we have no plans to do any further 7.17 releases, bearing any catastrophic bugs found, and this does not seem like it's the case. We would be open to making the change against main, and perhaps backport it to 8.19. Yet we need to work on adding tests and better understanding the usecase and gain. Correct me if I am wrong but I care to specify that this isn't a change to the match query of the query DSL, but to the named queries feature. Thanks again! |
I aggree making the change against main |
Using Lucene's Two Phase Query to submit and optimize the match query, the query has been tested and found to be problem free