[
https://issues.apache.org/jira/browse/HBASE-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127071#comment-13127071
]
Jonathan Gray commented on HBASE-4469:
--------------------------------------
Thanks Liyin. Unfortunately because the RB integration isn't very tight, to
follow Apache protocol, you need to attach the patch to the JIRA and select the
radio button that assigns it to apache.
This also helps to ensure that there's no confusion about which version was
committed and that we don't have a hard dependency on RB in any way.
It'll all be second nature before you know it :)
> 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
> 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
