[
https://issues.apache.org/jira/browse/HBASE-10885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated HBASE-10885:
-------------------------------------------
Release Note:
Deletes can be specified with Cell Visibility as done for puts.
Cells covered by the delete is found by doing pattern matching.
A deleteFamily issued for row1, f1 with Cell Visibility (A & B) would delete
only those cells of row1 under family f1 which has cell visibility A&B or B&A.
A delete without any cell visibility would only delete those cells that does
not have any cell visibility.
In case of delete specific column with latest version only the latest cell with
the specified cell visibility will be covered by the delete marker. In case
there is no such cell with the specified cell visibility then no cell gets
deleted.
was:
Deletes can be specified with Cell Visibility as done for puts.
Cells covered by the delete is found by doing pattern matching.
A deleteFamily issued for row1, f1 with Cell Visibility (A & B) would delete
only those cells of row1 under family f1 which has cell visibility A&B or B&A.
A delete without any cell visibility would only delete those cells that does
not have any cell visibility.
> 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
> Assignee: ramkrishna.s.vasudevan
> Priority: Blocker
> Fix For: 0.99.0, 0.98.4, 2.0.0
>
> Attachments:
> 10885-org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDeletes-output.txt,
> HBASE-10885_0.98_1.patch, HBASE-10885_1.patch, HBASE-10885_2.patch,
> HBASE-10885_branch_1.patch, HBASE-10885_new_tag_type_1.patch,
> HBASE-10885_new_tag_type_2.patch, HBASE-10885_v1.patch,
> HBASE-10885_v12.patch, HBASE-10885_v12.patch, HBASE-10885_v13.patch,
> HBASE-10885_v15.patch, HBASE-10885_v17.patch, HBASE-10885_v17.patch,
> HBASE-10885_v2.patch, HBASE-10885_v2.patch, HBASE-10885_v2.patch,
> HBASE-10885_v3.patch, HBASE-10885_v4.patch, HBASE-10885_v5.patch,
> HBASE-10885_v7.patch, HBASE-10885_v8.patch, HBASE-10885_v9.patch
>
>
> 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 of any visibility expression scoping. 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)
