Elasticsearch : Difference between "Range filter" and "Numeric range Filter"

Question

Other than the fact that one is specifically for numerical values, how does the execution differ internally. The docs say :

Numeric Range Filter :

... works by loading all the relevant field values into memory, and checking for the relevant docs if they satisfy the range requirements. This requires more memory..

Range Filter :

Has 2 execution options : (i) index (uses inverted index) (ii) fielddata (loads field data in memory)

Question:

Will the fielddata option of Range filter make it behave similar to Numeric range filter
Why doesn't the Numeric range filter have an index option?
The docs further say for small ranges the index execution is faster: What's considered small here?

If someone can explain it with an example, that would really help.

Paul · Accepted Answer · 2015-04-10 11:12:08Z

1

The Numeric Range Filter is deprecated. According to the Java API, "This filter will be removed at some point in time in favor for the range filter with the execution mode fielddata."

I think "small" is relative to the full range of values for that field. The meaning of "small" is something you'll have to determine yourself through benchmarking because performance will depend on how much memory is allocated to Elasticsearch and the type of data stored in the field.

answered Apr 10, 2015 at 11:12

Paul

20.2k15 gold badges84 silver badges100 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Elasticsearch : Difference between "Range filter" and "Numeric range Filter"

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related