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
Deprecate numeric_range
filter, add a field data execution option to range filter
#4034
Labels
Comments
+1 |
ghost
assigned martijnvg
Nov 25, 2013
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Nov 25, 2013
…data` as values. Deprecated `numeric_range` filter in favor for the `range` filter with `fielddata` as execution. Closes elastic#4034
martijnvg
added a commit
that referenced
this issue
Nov 25, 2013
…data` as values. Deprecated `numeric_range` filter in favor for the `range` filter with `fielddata` as execution. Closes #4034
dadoonet
added a commit
to dadoonet/elasticsearch
that referenced
this issue
Aug 12, 2014
As done with elastic#4034, `numeric_range` filter has been deprecated since 1.0.0. Closes elastic#7108.
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
…data` as values. Deprecated `numeric_range` filter in favor for the `range` filter with `fielddata` as execution. Closes elastic#4034
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
numeric_range
is very confusing, at the end, the question is if range filter should be done using the index itself, or using field data (in memory). I suggest deprecatingnumeric_range
, and addingexecution
field torange
filter, with possible values ofindex
andfielddata
. Thenumeric_range
filter will be removed in the next major version after 1.0.If its set to
fielddata
, we simply try and execute it using it (and if a mapper doesn't implement it, we simply fail the execution with unsupported exception).The text was updated successfully, but these errors were encountered: