[
https://issues.apache.org/jira/browse/HBASE-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kannan Muthukkaruppan updated HBASE-4469:
-----------------------------------------
Description:
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.
was:
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 will be added to bloomfilter. We can
take advantage of this factor to avoid seeking to the top of row.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
