[DOCS] Documented index.codec.bloom.load for #4525
This commit is contained in:
parent
51dc057244
commit
2b8c82c883
|
@ -141,6 +141,30 @@ following options:
|
|||
|
||||
Type name: `bloom`
|
||||
|
||||
[[codec-bloom-load]]
|
||||
[TIP]
|
||||
==================================================
|
||||
|
||||
It can sometime make sense to disable bloom filters. For instance, if you are
|
||||
logging into an index per day, and you have thousands of indices, the bloom
|
||||
filters can take up a sizable amount of memory. For most queries you are only
|
||||
interested in recent indices, so you don't mind queries on older indices
|
||||
taking slightly longer.
|
||||
|
||||
In these cases you can disable loading of the bloom filter on a per-index
|
||||
basis by updating the index settings:
|
||||
|
||||
[source,js]
|
||||
--------------------------------------------------
|
||||
PUT /old_index/_settings?index.codec.bloom.load=false
|
||||
--------------------------------------------------
|
||||
|
||||
This setting, which defaults to `true`, can be updated on a live index. Note,
|
||||
however, that changing the value will cause the index to be reopened, which
|
||||
will invalidate any existing caches.
|
||||
|
||||
==================================================
|
||||
|
||||
[float]
|
||||
[[pulsing-postings]]
|
||||
==== Pulsing postings format
|
||||
|
|
|
@ -59,6 +59,10 @@ settings API:
|
|||
`index.codec`::
|
||||
Codec. Default to `default`.
|
||||
|
||||
`index.codec.bloom.load`::
|
||||
Whether to load the bloom filter. Defaults to `true`.
|
||||
See <<bloom-postings>>.
|
||||
|
||||
`index.fail_on_merge_failure`::
|
||||
Default to `true`.
|
||||
|
||||
|
|
Loading…
Reference in New Issue