Match query with operator and, cutoff_frequency and stacked tokens #6573
Conversation
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
|
LGTM |
If the match query with cutoff_frequency encounters stacked tokens, like synonyms in the same position, it returns a boolean query instead of a common terms query. However, if the original operator was set to "and", it was ignoring that and resetting the operator to "or". In fact, if operator is "and" then there is little benefit in using a common terms query as a must query is already executed efficiently.
clintongormley
added a commit
that referenced
this pull request
Jun 25, 2014
If the match query with cutoff_frequency encounters stacked tokens, like synonyms in the same position, it returns a boolean query instead of a common terms query. However, if the original operator was set to "and", it was ignoring that and resetting the operator to "or". In fact, if operator is "and" then there is little benefit in using a common terms query as a must query is already executed efficiently. Closes #6573
clintongormley
changed the title
clintongormley
changed the title
clintongormley
added
the
:Search/Search
clintongormley
changed the title
mute
pushed a commit
to mute/elasticsearch
that referenced
this pull request
Jul 29, 2015
If the match query with cutoff_frequency encounters stacked tokens, like synonyms in the same position, it returns a boolean query instead of a common terms query. However, if the original operator was set to "and", it was ignoring that and resetting the operator to "or". In fact, if operator is "and" then there is little benefit in using a common terms query as a must query is already executed efficiently. Closes elastic#6573
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If the match query with cutoff_frequency encounters stacked tokens,
like synonyms in the same position, it returns a boolean query instead
of a common terms query. However, if the original operator was set
to "and", it was ignoring that and resetting the operator to "or".
In fact, if operator is "and" then there is little benefit in using
a common terms query as a must query is already
executed efficiently.
Fixed by 30c8031