-
Notifications
You must be signed in to change notification settings - Fork 25k
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 query analyzer logic for mixed conjunctions of terms and ranges #49803
Merged
romseygeek
merged 6 commits into
elastic:master
from
romseygeek:percolator-test-failure
Dec 10, 2019
Merged
Changes from 2 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
4e31ea6
Fix query analyzer logic for mixed conjunctions of terms and ranges
romseygeek 85dba06
some more tests
romseygeek 62d30e6
more testing, tweak msm logic
romseygeek d3fba98
Merge remote-tracking branch 'origin/master' into percolator-test-fai…
romseygeek f5e4e0f
feedback
romseygeek 6d91f8d
Don't reduce msm twice for duplicate range extractions
romseygeek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1208,4 +1208,51 @@ public void testIntervalQueries() { | |
assertTermsEqual(result.extractions, new Term("field", "a")); | ||
} | ||
|
||
public void testCombinedRangeAndTermWithMinimumShouldMatch() { | ||
|
||
Query disj = new BooleanQuery.Builder() | ||
.add(IntPoint.newRangeQuery("i", 0, 10), Occur.SHOULD) | ||
.add(new TermQuery(new Term("f", "v1")), Occur.SHOULD) | ||
.add(new TermQuery(new Term("f", "v1")), Occur.SHOULD) | ||
.setMinimumNumberShouldMatch(2) | ||
.build(); | ||
|
||
Result r = analyze(disj, Version.CURRENT); | ||
assertThat(r.minimumShouldMatch, equalTo(1)); | ||
|
||
Query q = new BooleanQuery.Builder() | ||
.add(IntPoint.newRangeQuery("i", 0, 10), Occur.SHOULD) | ||
.add(new TermQuery(new Term("f", "v1")), Occur.SHOULD) | ||
.add(new TermQuery(new Term("f", "v1")), Occur.SHOULD) | ||
.add(new TermQuery(new Term("f", "v1")), Occur.FILTER) | ||
.setMinimumNumberShouldMatch(2) | ||
.build(); | ||
|
||
Result result = analyze(q, Version.CURRENT); | ||
assertThat(result.minimumShouldMatch, equalTo(1)); | ||
assertThat(result.extractions.size(), equalTo(2)); | ||
assertFalse(result.verified); | ||
|
||
q = new BooleanQuery.Builder() | ||
.add(q, Occur.MUST) | ||
.add(q, Occur.MUST) | ||
.build(); | ||
|
||
result = analyze(q, Version.CURRENT); | ||
assertThat(result.minimumShouldMatch, equalTo(1)); | ||
assertThat(result.extractions.size(), equalTo(2)); | ||
assertFalse(result.verified); | ||
|
||
Query q2 = new BooleanQuery.Builder() | ||
.add(new TermQuery(new Term("f", "v1")), Occur.FILTER) | ||
.add(IntPoint.newRangeQuery("i", 15, 20), Occur.SHOULD) | ||
.add(new TermQuery(new Term("f", "v2")), Occur.SHOULD) | ||
.add(new TermQuery(new Term("f", "v2")), Occur.MUST) | ||
.setMinimumNumberShouldMatch(1) | ||
.build(); | ||
|
||
result = analyze(q2, Version.CURRENT); | ||
assertThat(result.minimumShouldMatch, equalTo(2)); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. let's maybe also have a test for the case that there are multiple range queries on the same field, or multiple range queries on different fields? |
||
} | ||
|
||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
can you count the number of extractions and check
verified
for all queries?