Remove Bloom filter and friends entirely #8571
Labels
Comments
s1monw
added
>enhancement
v2.0.0-beta1
good first issue
Closed
rmuir
added a commit
that referenced
this issue
Nov 21, 2014
make the "es090" postings format read-only, just to support old segments. There is a test version that subclasses it with write-capability for testing. Closes #8571 Conflicts: docs/reference/indices/update-settings.asciidoc src/main/java/org/elasticsearch/index/codec/postingsformat/BloomFilterPostingsFormat.java src/main/java/org/elasticsearch/index/codec/postingsformat/Elasticsearch090PostingsFormat.java src/main/java/org/elasticsearch/index/codec/postingsformat/PostingFormats.java src/test/java/org/elasticsearch/index/codec/postingformat/DefaultPostingsFormatTests.java src/test/java/org/elasticsearch/index/codec/postingformat/ElasticsearchPostingsFormatTest.java src/test/java/org/elasticsearch/search/suggest/completion/CompletionPostingsFormatTest.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have several issues related to the bloom filter mainly related to memory consumption etc. We disabled it by default on the loading end in
1.4.0which hasn't show any performance downsides yet. IMO we should remove the support of writing the bloomfilter entirely. In-fact since it's just delegating to another postings format we can even drop the reading code and remove this feature entirely. We should do this for2.0and1.xThe text was updated successfully, but these errors were encountered: