Hi Shrikant,
Kylin use FuzzyRowFilter instead of Bloom Filter. FuzzyRowFilter can find the row key which matches the specific pattern and skip scanning the records. It is more suitable than bloom filter for kylin in most cases. https://sematext.com/blog/consider-using-fuzzyrowfilter-when-in-need-for-secondary-indexes-in-hbase/ Hope this can help. Regards, Yichen [https://sematext.com/wp-content/uploads/2018/10/sematext-featured-image.png]<https://sematext.com/blog/consider-using-fuzzyrowfilter-when-in-need-for-secondary-indexes-in-hbase/> HBase FuzzyRowFilter: Alternative to Secondary Indexes ...<https://sematext.com/blog/consider-using-fuzzyrowfilter-when-in-need-for-secondary-indexes-in-hbase/> sematext.com In this post we’ll explain the usage of FuzzyRowFilter which can help in many situations where secondary indexes solutions seems to be the only choice to avoid full table scans. Background When it comes to HBase the way you design […] ________________________________ 发件人: Shrikant Bang <b.shrikan...@gmail.com> 发送时间: 2018年10月25日 17:05:44 收件人: d...@kylin.apache.org; user@kylin.apache.org 主题: Default Bloom Filters for HTables Hi Team, With my understanding, in Kylin v2.5.x bloom filters are disabled<https://github.com/apache/kylin/blob/2.5.x/storage-hbase/src/main/java/org/apache/kylin/storage/hbase/steps/CubeHTableUtil.java#L204> by default for HTables. I am curious to know if there is any specific reason using BloomType.NONE? Please correct me if I am wrong. Thank You, Shrikant Bang
