-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Fix LTR query feature with phrases (and two-phase) queries #125103
Conversation
Query features should verify that docs match the two-phase iterator.
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
Hi @jimczi, I've created a changelog YAML for you. |
I ran the updated test 1k times locally and still got failures:
another example:
One more:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💔 Backport failed
You can use sqren/backport to manually backport by running |
…25103) Query features should verify that docs match the two-phase iterator.
…25103) Query features should verify that docs match the two-phase iterator.
…25103) Query features should verify that docs match the two-phase iterator.
Follow up of elastic#125103 that leverages scorer supplier to create queries optimised to run on top docs only.
Follow up of #125103 that leverages scorer supplier to create queries optimised to run on top docs only.
Follow up of elastic#125103 that leverages scorer supplier to create queries optimised to run on top docs only.
…25103) Query features should verify that docs match the two-phase iterator.
Follow up of elastic#125103 that leverages scorer supplier to create queries optimised to run on top docs only.
…25103) Query features should verify that docs match the two-phase iterator.
Follow up of elastic#125103 that leverages scorer supplier to create queries optimised to run on top docs only.
LTR Query features should verify that docs match the two-phase iterator.