Clever Geek Handbook

Elasticsearch: Difference Between "Range Filter" and "Digital Range Filter"

Apart from the fact that it is specific for numeric values, how the execution differs from the internal one. The docs say:

Digital range filter :

... works by loading all the relevant field values ​​into memory and checking the relevant documents if they meet the range requirements. This requires more memory.

Range filter :

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

Question:

  • Will the parameter fielddata

    Range filter

    make it look likeNumeric range filter

  • Why Numeric range filter

    does the parameter have an index parameter?
  • The docs also say for small ranges the index execution is faster

    : What counts small

    here?

If anyone can explain this with an example it will really help.

+3


source to share


1 answer


The digital range filter is obsolete. According to the Java API , "This filter will be removed at some point in time in favor of a range filter with run mode field parameters."



I think "small" refers to the full range of values ​​for that field. The meaning of "small" is something that you will need to determine yourself using benchmarking, since performance will depend on how much memory Elasticsearch is allocated and the type of data stored in the field.

+1


source






More articles:


All Articles