[jira] [Updated] (HBASE-5032) Add DELETE COLUMN into the delete bloom filter

["Zhihong Yu (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhihong Yu updated HBASE-5032:
------------------------------

    Description: 
Previously, the delete family bloom filter only contains the row key which has the delete family. It helps us to avoid the top-row seek operation.

This jira attempts to add the delete column into this delete bloom filter as well (rename the delete family bloom filter as delete bloom filter).

The motivation is to save seek ops for scan time-range queries if we know there is no delete column for this row/column. 
We can seek directly to the exact timestamp we are interested in, instead of seeking to the latest timestamp and keeping skipping to find out whether there is any delete column before the interested timestamp.



  was:
Previously, the delete family bloom filter only contains the row key which has the delete family. It helps us to avoid the top-row seek operation.

This jira attempts to add the delete column into this delete bloom filter as well (rename the delete family bloom filter as delete bloom filter).

The motivation is to save seek ops for scan time-range queries if we know there is no delete column for this row/column. 
We can seek directly to the exact timestamp we are interested in, instead of seeking to the latest timestamp and keeping skipping to found out whether there is any delete column before the interested timestamp.



    
> Add DELETE COLUMN into the delete bloom filter
> ----------------------------------------------
>
>                 Key: HBASE-5032
>                 URL: https://issues.apache.org/jira/browse/HBASE-5032
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>
> Previously, the delete family bloom filter only contains the row key which has the delete family. It helps us to avoid the top-row seek operation.
> This jira attempts to add the delete column into this delete bloom filter as well (rename the delete family bloom filter as delete bloom filter).
> The motivation is to save seek ops for scan time-range queries if we know there is no delete column for this row/column. 
> We can seek directly to the exact timestamp we are interested in, instead of seeking to the latest timestamp and keeping skipping to find out whether there is any delete column before the interested timestamp.

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