From dea6b112ae0951d260223aac79eaf09b0c12f3d4 Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Fri, 20 Dec 2013 11:20:54 +0100 Subject: [PATCH] [DOCS] Corrected bloom loading docs --- docs/reference/index-modules/codec.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/index-modules/codec.asciidoc b/docs/reference/index-modules/codec.asciidoc index 47491087616..f53c18fa668 100644 --- a/docs/reference/index-modules/codec.asciidoc +++ b/docs/reference/index-modules/codec.asciidoc @@ -148,8 +148,8 @@ Type name: `bloom` 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. +interested in recent indices, so you don't mind CRUD operations 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: