Fixed QueryParsingException in multi match query #19564
Merged
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
…ession results in no fields. The query will now return 0 hits (null query) instead of throwing an exception. This matches the behavior if a nonexistent field is specified. These changes were backported from latest master (mostly from elastic#13405).
|
Can one of the admins verify this patch? |
clintongormley
added
>enhancement
review
:Search/Search
|
@cbuescher could you review this please? |
|
@qwerty4030 thanks for backporting this fix, LGTM. As you mentioned, this is very close to how wildcards in fieldnames are handled on master currently. |
clintongormley
added
:Search/Search
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.
Fixed QueryParsingException in multi match query when a wildcard expression results in no fields.
The query will now return 0 hits (null query) instead of throwing an exception. This matches the behavior if a nonexistent field is specified.
These changes were backported from latest master (mostly from #13405).
All test pass when I ran
mvn clean verifyCloses #16098