hbase-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/HBASE-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192016#comment-13192016

Lars Hofhansl commented on HBASE-5268:

When I muck with KeyValue.KeyComparator to always sort prefix delete marker before all columns
with the same prefix regardless of TS, then I see the opposite scenario that in the setup
above the column delete marker is ignored and hence the newly put version of column 123 is
visible again. This is the because the column marker is considered less specific and hence
won't override the column prefix marker. Arghh :)

So ScanDeleteTracker would need to be completely refactored in order to keep prefix marker
separate from column and version markers.
The question is: Is that worth the risk, added code entropy, and effort, or can we document
that prefix delete markers should not be used together with column delete markers (where the
column markers column is identical to the prefix marker's column prefix, which does not make
much sense anyway)?

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


View raw message