[jira] [Created] (HBASE-9570) With AccessDeniedException, HBase shell would be better to just display the error message to be user friendly

["Yang Wang (JIRA)" <ji...@apache.org>]

Yang Wang created HBASE-9570:
--------------------------------

             Summary: With AccessDeniedException, HBase shell would be better to just display the error message to be user friendly
                 Key: HBASE-9570
                 URL: https://issues.apache.org/jira/browse/HBASE-9570
             Project: HBase
          Issue Type: Improvement
          Components: shell
            Reporter: Yang Wang


When access unauthorized resource like table, AccessDeniedException will be thrown. In HBase shell, the error message with stack trace will be displayed as follows. It would be better to just display the error message avoiding the stack trace to be user friendly. 
{noformat}
ERROR: org.apache.hadoop.hbase.security.AccessDeniedException: Insufficient permissions for user 'u1' for scanner open on table t1
        at org.apache.hadoop.hbase.security.access.AccessController.preScannerOpen(AccessController.java:1116)
        at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.preScannerOpen(RegionCoprocessorHost.java:1293)
        at org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3026)
        at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26971)
        at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2083)
        at org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1820)
        at org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:165)
        at org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:41)
        at org.apache.hadoop.hbase.ipc.SimpleRpcScheduler$1.run(SimpleRpcScheduler.java:113)
        at java.lang.Thread.run(Thread.java:662)
{noformat}

--
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