More documentation improvements for fielddata loading.
This commit is contained in:
parent
07443089ce
commit
52db8eb324
|
@ -92,8 +92,8 @@ field data format.
|
||||||
[float]
|
[float]
|
||||||
=== Fielddata loading
|
=== Fielddata loading
|
||||||
|
|
||||||
By default, field data is loaded lazily, on the first time that a query that
|
By default, field data is loaded lazily, ie. the first time that a query that
|
||||||
requires field data is fired. However, this can make the first requests that
|
requires them is executed. However, this can make the first requests that
|
||||||
follow a merge operation quite slow since fielddata loading is a heavy
|
follow a merge operation quite slow since fielddata loading is a heavy
|
||||||
operation.
|
operation.
|
||||||
|
|
||||||
|
@ -118,9 +118,9 @@ It is possible to force field data to be loaded and cached eagerly through the
|
||||||
Field data can take a lot of RAM so it makes sense to disable field data
|
Field data can take a lot of RAM so it makes sense to disable field data
|
||||||
loading on the fields that don't need field data, for example those that are
|
loading on the fields that don't need field data, for example those that are
|
||||||
used for full-text search only. In order to disable field data loading, just
|
used for full-text search only. In order to disable field data loading, just
|
||||||
change the field data format to `disabled`. Request that will try to load field
|
change the field data format to `disabled`. When disabled, all requests that
|
||||||
data on any field which is configured with this format will then return an
|
will try to load field data, e.g. when they include aggregations and/or sorting,
|
||||||
error.
|
will return an error.
|
||||||
|
|
||||||
[source,js]
|
[source,js]
|
||||||
--------------------------------------------------
|
--------------------------------------------------
|
||||||
|
|
Loading…
Reference in New Issue