Docs: Remove the note that fielddata doesn't support filtering.
This particular note was about fielddata filtering but could cause confusion that fields that have doc values enabled cannot be used for filtering (as in a `filtered_query`).
This commit is contained in:
parent
e9f05eed80
commit
491a48e55b
|
@ -128,7 +128,7 @@ field data format.
|
||||||
`doc_values`::
|
`doc_values`::
|
||||||
Computes and stores field data data-structures on disk at indexing time.
|
Computes and stores field data data-structures on disk at indexing time.
|
||||||
Lowers memory usage but only works on non-analyzed strings (`index`: `no` or
|
Lowers memory usage but only works on non-analyzed strings (`index`: `no` or
|
||||||
`not_analyzed`) and doesn't support <<field-data-filtering,filtering>>.
|
`not_analyzed`).
|
||||||
|
|
||||||
[float]
|
[float]
|
||||||
==== Numeric field data types
|
==== Numeric field data types
|
||||||
|
@ -138,7 +138,6 @@ field data format.
|
||||||
|
|
||||||
`doc_values`::
|
`doc_values`::
|
||||||
Computes and stores field data data-structures on disk at indexing time.
|
Computes and stores field data data-structures on disk at indexing time.
|
||||||
Doesn't support <<field-data-filtering,filtering>>.
|
|
||||||
|
|
||||||
[float]
|
[float]
|
||||||
==== Geo point field data types
|
==== Geo point field data types
|
||||||
|
|
Loading…
Reference in New Issue