[
https://issues.apache.org/jira/browse/HBASE-11054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980486#comment-13980486
]
Andrew Purtell commented on HBASE-11054:
----------------------------------------
bq. As for this patch. Is a coprocessor the right approach? Or should the class
be pluggable?
The component that would use this functionality would be the
VisibilityController, which is a coprocessor, operating potentially on some
regions but not others.
bq. There are only filters, and all logic is expressed in series of filters. No
more deleteTrackers or columnTrackers.
That could be fine on trunk but can't happen in 0.98, where we have HBASE-10885
as an important objective.
> 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)
