Docs: fix documentation for bloom filter defaults

This commit is contained in:
mikemccand 2014-07-27 18:39:29 -04:00
parent c367ae09e3
commit 96ecec34d1
1 changed files with 5 additions and 5 deletions

View File

@ -145,17 +145,17 @@ Type name: `bloom`
================================================== ==================================================
As of 1.4, the bloom filters are no longer loaded at search time by As of 1.4, the bloom filters are no longer loaded at search time by
default: they consume ~10 bits per unique id value, which can quickly default: they consume RAM in proportion to the number of unique terms,
add up for indices with many tiny documents, and separate performance which can quickly add up for certain use cases, and separate
improvements have made the performance gains with bloom filters very performance improvements have made the performance gains with bloom
small. filters very small.
You can enable loading of the bloom filter at search time on a You can enable loading of the bloom filter at search time on a
per-index basis by updating the index settings: per-index basis by updating the index settings:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
PUT /old_index/_settings?index.codec.bloom.load=false PUT /old_index/_settings?index.codec.bloom.load=true
-------------------------------------------------- --------------------------------------------------
This setting, which defaults to `false`, can be updated on a live index. Note, This setting, which defaults to `false`, can be updated on a live index. Note,