hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liyin Tang (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4469) Avoid top row seek by looking up bloomfilter
Date Thu, 13 Oct 2011 17:57:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126760#comment-13126760
] 

Liyin Tang commented on HBASE-4469:
-----------------------------------

@stack. HBASE-4469 optimizes the top row seek if the ROWCOL Bloom filter is enabled.
And HBASE-4532  will optimize the top row seek if ROW or NONE Bloom filter is enabled.
So HBASE-4469 + HBASE-4532 will optimize all the cases.
 
And it is necessary to commit this first:)

                
> Avoid top row seek by looking up bloomfilter
> --------------------------------------------
>
>                 Key: HBASE-4469
>                 URL: https://issues.apache.org/jira/browse/HBASE-4469
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>
> The problem is that when seeking for the row/col in the hfile, we will go to top of the
row in order to check for row delete marker (delete family). However, if the bloomfilter is
enabled for the column family, then if a delete family operation is done on a row, the row
is already being added to bloomfilter. We can take advantage of this factor to avoid seeking
to the top of row.

--
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

        

Mime
View raw message