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

stack commented on HBASE-11791:
-------------------------------

+1 from me.  Its a great read.  Big improvement.  Can work on teething problem 
in new issues.  Fix below on commit:

        753                   <para>Superusers are specified as a 
comma-separated list of users and groups, in the
754                       <option>hbase.superuser</option> option in 
<filename>hbase-site.xml</filename>,
755                     has global scope in HBase. The superuser is equivalent 
to the

An example would help here but that can be done in another issue:

f you use the AccessController along with the VisibilityController, the
797                   AccessController must come first in the list, because 
with both components active, the
798                   VisibilityController will delegate access control on its 
system tables to the
799                   AccessController.

(You actually have an illustration later in the patch   1785      
<name>hbase.coprocessor.regionserver.classes</name>
1786      <value>org.apache.hadoop/hbase.security.access.AccessController,
1787      org.apache.hadoop.hbase.security.access.VisibilityController</value>)

Fix this..

Neither these examples example, nor 

Do you want to say the below is the default in hbase 1.0?

"You also need to be sure your HFiles use HFile v3..."



> Update docs on visibility tags and ACLs, transparent encryption, secure bulk 
> upload
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-11791
>                 URL: https://issues.apache.org/jira/browse/HBASE-11791
>             Project: HBase
>          Issue Type: Task
>          Components: documentation
>            Reporter: Misty Stanley-Jones
>            Assignee: Misty Stanley-Jones
>         Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, 
> HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, 
> HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, 
> HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v2.patch, 
> HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, 
> HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase 
> Security Features Operators Guide - HBaseCon 2014 - v5.pptx, 
> LDAPScanLabelGenerator.png
>
>
> Do a pass on the ACL and tag docs and make sure they are up to date and 
> accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to