-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CI] org.elasticsearch.percolator.CandidateQueryTests.testDuel failure #50305
Labels
:Search Relevance/Percolator
Reverse search: find queries that match a document
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
>test-failure
Triaged test failures from CI
Comments
martijnvg
added
>test-failure
Triaged test failures from CI
:Search Relevance/Percolator
Reverse search: find queries that match a document
labels
Dec 18, 2019
Pinging @elastic/es-search (:Search/Percolator) |
This is a slightly different instance of this failure, which I expect to be related:
Build urls:
This also reproduces for me:
|
Other instances of this failure: |
romseygeek
added a commit
that referenced
this issue
Jan 7, 2020
With the rewrite of the percolator's QueryAnalyzer to use lucene's QueryVisitor API, term queries that are direct children of a boolean query are handled separately from other children. This works fine for conjunctions, but for disjunctions we need to treat the extracted terms from these direct descendents along with extractions from more deeply nested children to ensure that minimum-should-match requirements are met correctly. This commit changes the logic in QueryAnalyzer#getResult() to bundle child term results with all other results before handling them. Fixes #50305
romseygeek
added a commit
that referenced
this issue
Jan 7, 2020
With the rewrite of the percolator's QueryAnalyzer to use lucene's QueryVisitor API, term queries that are direct children of a boolean query are handled separately from other children. This works fine for conjunctions, but for disjunctions we need to treat the extracted terms from these direct descendents along with extractions from more deeply nested children to ensure that minimum-should-match requirements are met correctly. This commit changes the logic in QueryAnalyzer#getResult() to bundle child term results with all other results before handling them. Fixes #50305
SivagurunathanV
pushed a commit
to SivagurunathanV/elasticsearch
that referenced
this issue
Jan 23, 2020
With the rewrite of the percolator's QueryAnalyzer to use lucene's QueryVisitor API, term queries that are direct children of a boolean query are handled separately from other children. This works fine for conjunctions, but for disjunctions we need to treat the extracted terms from these direct descendents along with extractions from more deeply nested children to ensure that minimum-should-match requirements are met correctly. This commit changes the logic in QueryAnalyzer#getResult() to bundle child term results with all other results before handling them. Fixes elastic#50305
This was referenced Feb 3, 2020
javanna
added
the
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
label
Jul 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Search Relevance/Percolator
Reverse search: find queries that match a document
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
>test-failure
Triaged test failures from CI
This failure does reproduce locally for me.
Build urls:
The text was updated successfully, but these errors were encountered: