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

Hudson commented on HBASE-10326:
--------------------------------

SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-1.1 #52 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/52/])
HBASE-10326 Super user should be able scan all the cells irrespective of the 
visibility labels(Ram) (anoopsamjohn: rev 1557792)
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/security/visibility/VisibilityController.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/security/visibility/TestVisibilityLabels.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/security/visibility/TestVisibilityLabelsWithACL.java


> Super user should be able scan all the cells irrespective of the visibility 
> labels
> ----------------------------------------------------------------------------------
>
>                 Key: HBASE-10326
>                 URL: https://issues.apache.org/jira/browse/HBASE-10326
>             Project: HBase
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 0.98.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Critical
>              Labels: security
>             Fix For: 0.98.0, 0.99.0
>
>         Attachments: HBASE-10326.patch, HBASE-10326_1.patch
>
>
> This issue is in lieu with HBASE-10322.  In case of export tool, when the 
> cells with visibility labels are exported using a super user we should be 
> able to export the data.  But with the current implementation, the super user 
> would also be able to view cells that has visibility labels associated with 
> the superuser.  The idea of HBASE-10322 is to strip out tags based on user 
> and if so this change is necessary for export tool to work with Visibility.  
> ACL already has a concept of global admins.  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to