Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 25 Jan 2012 00:32:40 +0000 (UTC)
From: "Lars Hofhansl (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1358301720.74841.1327451560540.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1901569009.70402.1327383820983.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5268) Add delete column prefix delete
 marker
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl commented on HBASE-5268:
--------------------------------------

Hmm... Good point. Isn't that the same for a column delete with many versions that span many blocks, though? In that case the ScanDeleteTracker would need to hold on to all prefix markers.
I.e. there might be a prefix marker for 123 at T and then one for 1234 at T+A and another one for 12345 at T+A+B. They would need to stored and checked every time based on the TS of the rows they affect.

I'll try the Get part.
                
> 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