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 23:24:11 GMT

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

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

@Jonathan, 
For this jira specifically, it has been committed to 89-fb internal branch before cutting
the public 89-fb branch.
So it should already in the public 89-fb right now.



                
> 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
>             Fix For: 0.94.0
>
>         Attachments: HBASE-4469_1.patch
>
>
> 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