hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5268) Add delete column prefix delete marker
Date Wed, 25 Jan 2012 00:22:40 GMT

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

Todd Lipcon commented on HBASE-5268:

I can't see how that's correct. Let's say instead of just two columns with colb_* we had a
few thousand, such that it spanned many blocks. Then we requested a get with only the column
colb_2000. The optimizations that Mikhail described at the HUG last week would assumedly want
to seek directly to that block, but with the delete marker somewhere "in the middle" we'd
be forced to scan forward from the beginning of the whole row looking for potential deletions
somewhere along the way. Right?

I think the delete prefix markers would have to go at the very top of the row, alongside the
"delete family" markers (since we already force a top-of-row seek to look for delete-family,
assuming lack of a deletion bloom).
> 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-v4.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


View raw message