4e7ce4ee02
This commit changes field data configuration updates so that they are immediately taken into account for loading new segments. The way it works is that field data configuration is now cached separately from the field data cache, meaning that it is now possible to clear the field data configuration from IndexFieldDataService while the cache will stay around. On the next time that Elasticsearch will reload field data configuration, it will check if there is already a cache entry, and reuse it if it exists. To disable field data loading, all that is required is to change the field data format to "none" (supported by all field data types) using the update mapping API. Elasticsearch will then refuse to load field data on any new segment, but field data which has been loaded on the previous segments will remain available. So you need to clear the field data cache in order to reclaim memory (otherwise memory will be reclaimed slower, as segments get merged). Close #4430 Close #4431 |
||
|---|---|---|
| .. | ||
| allocation.asciidoc | ||
| analysis.asciidoc | ||
| cache.asciidoc | ||
| codec.asciidoc | ||
| fielddata.asciidoc | ||
| mapper.asciidoc | ||
| merge.asciidoc | ||
| similarity.asciidoc | ||
| slowlog.asciidoc | ||
| store.asciidoc | ||
| translog.asciidoc | ||