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

Laxman commented on HBASE-6188:
-------------------------------

>From the log attached.
{noformat}
        at 
org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:347)
        at 
org.apache.hadoop.hbase.security.access.TestAccessController.setupBeforeClass(TestAccessController.java:123)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
{noformat}

>From TestAccessController.setupBeforeClass()
{code}
    HTableDescriptor htd = new HTableDescriptor(TEST_TABLE);
    htd.addFamily(new HColumnDescriptor(TEST_FAMILY));
    htd.setOwner(USER_OWNER);
    admin.createTable(htd);
{code}

This indicates acl is table is not yet online by the time of creation of test 
table.
A small delay (sleep for 1 sec) after starting the cluster may help to resolve 
this intermittent test failure.

Andy, I couldn't verify this its running fine in my local and QA build. Any 
other suggestions apart from introducing a delay?

                
> Remove the concept of table owner
> ---------------------------------
>
>                 Key: HBASE-6188
>                 URL: https://issues.apache.org/jira/browse/HBASE-6188
>             Project: HBase
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: 0.94.0, 0.96.0, 0.94.1
>            Reporter: Andrew Purtell
>            Assignee: Laxman
>              Labels: security
>             Fix For: 0.96.0, 0.94.1
>
>         Attachments: HBASE-6188.1.patch, HBASE-6188.2.patch, 
> HBASE-6188.3.patch, HBASE-6188.4.patch, HBASE-6188.patch, 
> org.apache.hadoop.hbase.security.access.TestAccessController.txt
>
>
> The table owner concept was a design simplification in the initial drop.
> First, the design changes under review means only a user with GLOBAL CREATE 
> permission can create a table, which will probably be an administrator.
> Then, granting implicit permissions may lead to oversights and it adds 
> unnecessary conditionals to our code. So instead the administrator with 
> GLOBAL CREATE permission should make the appropriate grants at table create 
> time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to