Has anyone had success adding a bloom filter to the codec for any of their fields?
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-codec.html#bloom-postings I imagine it'd help reduce IO from (non multi-term) queries that frequently don't match. Like if you have a field that is very specific and useful for searching but very rarely matches anything. It looks like the cost is in the range of 10 bits of heap per term per segment for a false positive probability around 1%. Meaning it'd be pretty high if the index had lots of terms - especially if they were in many segments. But it'd be about 10 bits per value if the values were mostly unique. Nik -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3X11bwogWi9oFTYFzzO6%2BdnvsOqcEFWG_dB5c%2Boy%3D4Fw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
