You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (Updated) (JIRA)" <ji...@apache.org> on 2011/10/13 17:04:12 UTC
[jira] [Updated] (HBASE-4532) Avoid top row seek by dedicated bloom
filter for delete family
[ https://issues.apache.org/jira/browse/HBASE-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-4532:
-------------------------
Comment: was deleted
(was: OK. I was confused. I'm +0 on this patch (since I am not familiar with what is going on here -- it looks innocuous enough). Jon you going to commit?)
> Avoid top row seek by dedicated bloom filter for delete family
> --------------------------------------------------------------
>
> Key: HBASE-4532
> URL: https://issues.apache.org/jira/browse/HBASE-4532
> Project: HBase
> Issue Type: Improvement
> Reporter: Liyin Tang
> Assignee: Liyin Tang
>
> HBASE-4469 avoids the top row seek operation if row-col bloom filter is enabled.
> This jira tries to avoid top row seek for all the cases by creating a dedicated bloom filter only for delete family.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira