[
https://issues.apache.org/jira/browse/HBASE-9285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747093#comment-13747093
]
Ted Yu commented on HBASE-9285:
-------------------------------
The javadoc warnings are not related to my patch:
{code}
[WARNING] Javadoc Warnings
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/MasterAdminProtos.java:33377:
warning - @return tag cannot be used in method with void return type.
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/MasterAdminProtos.java:32381:
warning - @return tag cannot be used in method with void return type.
{code}
> User who created table cannot scan the same table due to Insufficient
> permissions
> ---------------------------------------------------------------------------------
>
> Key: HBASE-9285
> URL: https://issues.apache.org/jira/browse/HBASE-9285
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.95.2
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 0.98.0, 0.96.0
>
> Attachments: 9285.patch
>
>
> User hrt_qa has been given 'C' permission.
> {code}
> create 'te', {NAME => 'f1', VERSIONS => 5}
> ...
> hbase(main):003:0> list
> TABLE
> hbase:acl
> hbase:namespace
> te
> 6 row(s) in 0.0570 seconds
> hbase(main):004:0> scan 'te'
> ROW COLUMN+CELL
> 2013-08-21 02:21:00,921 DEBUG [main] token.AuthenticationTokenSelector: No
> matching token found
> 2013-08-21 02:21:00,921 DEBUG [main] security.HBaseSaslRpcClient: Creating
> SASL GSSAPI client. Server's Kerberos principal name is
> hbase/[email protected]
> 2013-08-21 02:21:00,923 DEBUG [main] security.HBaseSaslRpcClient: Have sent
> token of size 582 from initSASLContext.
> 2013-08-21 02:21:00,926 DEBUG [main] security.HBaseSaslRpcClient: Will read
> input token of size 0 for processing by initSASLContext
> 2013-08-21 02:21:00,926 DEBUG [main] security.HBaseSaslRpcClient: Will send
> token of size 0 from initSASLContext.
> 2013-08-21 02:21:00,926 DEBUG [main] security.HBaseSaslRpcClient: Will read
> input token of size 53 for processing by initSASLContext
> 2013-08-21 02:21:00,927 DEBUG [main] security.HBaseSaslRpcClient: Will send
> token of size 53 from initSASLContext.
> 2013-08-21 02:21:00,927 DEBUG [main] security.HBaseSaslRpcClient: SASL client
> context established. Negotiated QoP: auth
> 2013-08-21 02:21:00,935 WARN [main] client.RpcRetryingCaller: Call
> exception, tries=0, retries=7, retryTime=-14ms
> org.apache.hadoop.hbase.security.AccessDeniedException:
> org.apache.hadoop.hbase.security.AccessDeniedException: Insufficient
> permissions for user 'hrt_qa' for scanner open on table te
> at
> org.apache.hadoop.hbase.security.access.AccessController.preScannerOpen(AccessController.java:1116)
> at
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preScannerOpen(RegionCoprocessorHost.java:1294)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3007)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26847)
> ...
> Caused by:
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.security.AccessDeniedException):
> org.apache.hadoop.hbase.security.AccessDeniedException: Insufficient
> permissions for user 'hrt_qa' for scanner open on table te
> at
> org.apache.hadoop.hbase.security.access.AccessController.preScannerOpen(AccessController.java:1116)
> at
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preScannerOpen(RegionCoprocessorHost.java:1294)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3007)
> {code}
> Here was related entries in hbase:acl table:
> {code}
> hbase(main):001:0> scan 'hbase:acl'
> ROW COLUMN+CELL
> hbase:acl column=l:hrt_qa,
> timestamp=1377045996685, value=C
> te column=l:hrt_qa,
> timestamp=1377051648649, value=RWXCA
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
