You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nicolas Spiegelberg (JIRA)" <ji...@apache.org> on 2010/04/23 21:08:51 UTC

[jira] Work started: (HBASE-1200) Add bloomfilters; use dynamicbloomfilter instead of base bloomfilter

     [ https://issues.apache.org/jira/browse/HBASE-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on HBASE-1200 started by Nicolas Spiegelberg.

> Add bloomfilters; use dynamicbloomfilter instead of base bloomfilter
> --------------------------------------------------------------------
>
>                 Key: HBASE-1200
>                 URL: https://issues.apache.org/jira/browse/HBASE-1200
>             Project: Hadoop HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: Nicolas Spiegelberg
>             Fix For: 0.21.0
>
>         Attachments: ryan_bloomfilter.patch
>
>
> Add bloomfiltering to hfile.  Should it be optional or on always?  Currently, we bloom filter rows only, not the column + ts component, which seems good place to start but we size the bloomfilter with the number of entries we are about to flush which seems like usually we'd be making a filter too big.  How to figure how many rows in the flush?   We should use the DynamicBloomFilter as Andrezj does up in hadoop BloomFilterMapFile.  Start small and let it resize as entries are added.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.