Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 24 Apr 2014 05:25:19 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12710011.1398253046805.169447.1398317119559@arcas>
In-Reply-To: <JIRA.12710011.1398253046805@arcas>
References: <JIRA.12710011.1398253046805@arcas>
Subject: [jira] [Commented] (HBASE-11054) Create new hook in StoreScanner to
 help user creating his own delete tracker
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl commented on HBASE-11054:
---------------------------------------

bq. By the time we call filterKV() in filters the cells masked by deletes are removed already. 
I meant generallt (not specifically the patch). We could be radical and say: There are only filters, and all logic is expressed in series of filters. No more deleteTrackers or columnTrackers.


> Create new hook in StoreScanner to help user creating his own delete tracker
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-11054
>                 URL: https://issues.apache.org/jira/browse/HBASE-11054
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 0.99.0, 0.98.2
>
>         Attachments: HBASE-11054.patch
>
>
> In case of Visibility labels, to support deletes we need to consider the visibility expression per version inorder to identify the matching visibility expression.  
> Tracking the visibility tags along with the delete tracker would make things easier rather than handling during scans/compactions.


--
This message was sent by Atlassian JIRA
(v6.2#6252)