Docs: Added link to clarify meaning of filtering in fielddata context
This commit is contained in:
parent
b43c2ced93
commit
f2aa4a38bc
|
@ -138,7 +138,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 filtering.
|
`not_analyzed`) and doesn't support <<field-data-filtering,filtering>>.
|
||||||
|
|
||||||
[float]
|
[float]
|
||||||
==== Numeric field data types
|
==== Numeric field data types
|
||||||
|
@ -148,7 +148,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.
|
||||||
Doesn't support filtering.
|
Doesn't support <<field-data-filtering,filtering>>.
|
||||||
|
|
||||||
[float]
|
[float]
|
||||||
==== Geo point field data types
|
==== Geo point field data types
|
||||||
|
|
Loading…
Reference in New Issue