hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5268) Add delete column prefix delete marker
Date Tue, 24 Jan 2012 20:18:40 GMT

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

Lars Hofhansl updated HBASE-5268:
---------------------------------

    Attachment: 5268-v3.txt

Sorting prefix markers first has another problem.
Placing a prefix marker for 123 at T and then another for 1234 at T+1 will ignore the 2nd
one even though it is for newer timestamp. To fix that ScanDeleteTracker would need to keep
track of delete marker that are prefixes of each other and would increase memory requirements.

So I am back to the first approach. It is simpler, does not much with the sort order, has
less memory requirements, and is easier to grok.
Delete.deleteColumnsByPrefix now advises against mixing this with deleteColumn for the *same*
qualifiers.

I added more test and propose this for commit.
                
> Add delete column prefix delete marker
> --------------------------------------
>
>                 Key: HBASE-5268
>                 URL: https://issues.apache.org/jira/browse/HBASE-5268
>             Project: HBase
>          Issue Type: Improvement
>          Components: client, regionserver
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 0.94.0
>
>         Attachments: 5268-v2.txt, 5268-v3.txt, 5268.txt
>
>
> This is another part missing in the "wide row challenge".
> Currently entire families of a row can be deleted or individual columns or versions.
> There is no facility to mark multiple columns for deletion by column prefix.
> Turns out that be achieve with very little code (it's possible that I missed some of
the new delete bloom filter code, so please review this thoroughly). I'll attach a patch soon,
just working on some tests now.

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