From b6b9ef8e26d5d3ce6acf5274e56d4f37e84af19a Mon Sep 17 00:00:00 2001 From: Lee Hinman Date: Wed, 29 Mar 2017 12:11:20 -0600 Subject: [PATCH] [DOCS] Remove line about eager loading global ordinals Fielddata can no longer be configured to be loaded eagerly (it only accepts `true` and `false`), so this line is a little misleading because it talks about a procedure we can no longer do. --- docs/reference/mapping/params/fielddata.asciidoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/reference/mapping/params/fielddata.asciidoc b/docs/reference/mapping/params/fielddata.asciidoc index 6795b0f5b9b..baca3c426d6 100644 --- a/docs/reference/mapping/params/fielddata.asciidoc +++ b/docs/reference/mapping/params/fielddata.asciidoc @@ -135,8 +135,7 @@ whenever a once new segment becomes visible. The loading time of global ordinals depends on the number of terms in a field, but in general it is low, since it source field data has already been loaded. The memory overhead of global ordinals is a small because it is very -efficiently compressed. Eager loading of global ordinals can move the loading -time from the first search request, to the refresh itself. +efficiently compressed. *****************************************