[
https://issues.apache.org/jira/browse/HBASE-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126651#comment-13126651
]
stack commented on HBASE-4469:
------------------------------
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 on review). Jon you going to commit?
> 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
