hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10885) Support visibility expressions on Deletes
Date Tue, 01 Apr 2014 09:23:17 GMT

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

ramkrishna.s.vasudevan commented on HBASE-10885:
------------------------------------------------

Delete.setCellVisibility() should be supported now. And these labels passed here will be only
a list of labels and not visibility expressions like A|B!C?
Which means if an existing put had A&B now the delete should pass A&B or it could
be A,B like how we pass for Authorization?

> Support visibility expressions on Deletes
> -----------------------------------------
>
>                 Key: HBASE-10885
>                 URL: https://issues.apache.org/jira/browse/HBASE-10885
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.98.1
>            Reporter: Andrew Purtell
>             Fix For: 0.99.0, 0.98.2
>
>
> Accumulo can specify visibility expressions for delete markers. During compaction the
cells covered by the tombstone are determined in part by matching the visibility expression.
This is useful for the use case of data set coalescing, where entries from multiple data sets
carrying different labels are combined into one common large table. Later, a subset of entries
can be conveniently removed using visibility expressions.
> Currently doing the same in HBase would only be possible with a custom coprocessor. Otherwise,
a Delete will affect all cells covered by the tombstone regardless if they are visible to
the user issuing the delete or not. This is correct behavior in that no data spill is possible,
but certainly could be surprising, and is only meant to be transitional. We decided not to
support visibility expressions on Deletes to control the complexity of the initial implementation.



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

Mime
View raw message