[
https://issues.apache.org/jira/browse/HBASE-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036706#comment-13036706
]
Mikhail Bautin commented on HBASE-3763:
---------------------------------------
@stack, Joydeep: we thought it would be good to keep the core HFile format v2
changes separate from the two features that depend on it (multi-level block
indexes and compound Bloom filters), so that even though we have one design doc
we can still have three separate JIRAs.
Regarding the question about keeping the Bloom filter in memory: in our current
design/implementation it will be cached and kept in memory as long as there is
enough room in the block cache. The Bloom filter index is loaded at open time,
but the individual chunks are loaded and cached as needed. However, we are
adding separate configuration settings to cache Bloom filter chunks (and block
index chunks) at write time, extending the existing cache-on-write setting for
data blocks, so that the effect will exactly as Joydeep described.
> Add Bloom Block Index Support
> -----------------------------
>
> Key: HBASE-3763
> URL: https://issues.apache.org/jira/browse/HBASE-3763
> Project: HBase
> Issue Type: Improvement
> Components: io, regionserver
> Affects Versions: 0.89.20100924, 0.90.0, 0.90.1, 0.90.2
> Reporter: Mikhail Bautin
> Assignee: Mikhail Bautin
> Priority: Minor
> Labels: hbase, performance
> Fix For: 0.89.20100924
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Add a way to save HBase Bloom filters into an array of Meta blocks instead of
> one big Meta block, and load only the blocks required to answer a query.
> This will allow us faster bloom load times for large StoreFiles & pave the
> path for adding Bloom Filter support to HFileOutputFormat bulk load.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
