[ https://issues.apache.org/jira/browse/HBASE-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818725#comment-13818725 ]
ramkrishna.s.vasudevan commented on HBASE-7663: ----------------------------------------------- +1. For now can move authorizations and acl things into that super class. > [Per-KV security] Visibility labels > ----------------------------------- > > Key: HBASE-7663 > URL: https://issues.apache.org/jira/browse/HBASE-7663 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors, security > Affects Versions: 0.98.0 > Reporter: Andrew Purtell > Assignee: Anoop Sam John > Fix For: 0.98.0 > > Attachments: HBASE-7663.patch, HBASE-7663_V2.patch, > HBASE-7663_V3.patch, HBASE-7663_V4.patch, HBASE-7663_V5.patch, > HBASE-7663_V6.patch > > > Implement Accumulo-style visibility labels. Consider the following design > principles: > - Coprocessor based implementation > - Minimal to no changes to core code > - Use KeyValue tags (HBASE-7448) to carry labels > - Use OperationWithAttributes# {get,set}Attribute for handling visibility > labels in the API > - Implement a new filter for evaluating visibility labels as KVs are streamed > through. > This approach would be consistent in deployment and API details with other > per-KV security work, supporting environments where they might be both be > employed, even stacked on some tables. > See the parent issue for more discussion. -- This message was sent by Atlassian JIRA (v6.1#6144)