Fix term(s) query for range field#25918
Merged
jpountz merged 2 commits intoelastic:masterfrom Jul 31, 2017
Merged
Conversation
Collaborator
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
jpountz
suggested changes
Jul 28, 2017
Contributor
jpountz
left a comment
There was a problem hiding this comment.
Can you add a test to RangeFieldTypeTests?
Author
Contributor
|
I'd rather like a unit test, maybe you can have a look at the existing tests we have for range queries in that test and make one for |
05e84ae to
1c8e911
Compare
Author
|
@jpountz Done |
Contributor
|
@scinconovetta Thanks! |
jpountz
approved these changes
Jul 31, 2017
jpountz
pushed a commit
that referenced
this pull request
Jul 31, 2017
jpountz
pushed a commit
that referenced
this pull request
Jul 31, 2017
jpountz
pushed a commit
that referenced
this pull request
Jul 31, 2017
This file contains hidden or 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
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.
No longer able to run a term(s) query on a
long_rangefield from v5.5.0 and later.Example query:
The following error message is produced:
java.lang.IllegalArgumentException: Field [iprange] of type [long_range] does not support range queriesThis occurs after the removal of the
rangeQuerydefinition inRangeFieldMapper.java(see commit) between v5.4.0 and v5.5.0. This caused the call torangeQueryinsidetermQueryto resort to therangeQueryinMappedFieldType.java, where the exception is thrown.I've modified the call to
rangeQueryintermQueryto do what it had been doing before the 5-length argument definition was removed: pass inShapeRelation.INTERSECTSbeforecontext.Example error message: