[jira] [Commented] (ACCUMULO-1018) Client does not give informative message when user can not read table

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

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

Christopher Tubbs commented on ACCUMULO-1018:
---------------------------------------------

Under what circumstances can a client not know which table it was trying to read when it got a permissions error? It seems to me that the client code should always have the table name when an exception occurs as a result of not having sufficient permissions. I imagine the observed behavior is the result of an application passing through an AccumuloSecurityException, instead of handling it properly. If that is the case, then this is a problem with the application using Accumulo, not Accumulo having insufficiently informative messages.
                
> Client does not give informative message when user can not read table
> ---------------------------------------------------------------------
>
>                 Key: ACCUMULO-1018
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1018
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>            Assignee: Billie Rinaldi
>             Fix For: 1.6.0
>
>
> Saw this in 1.4, not sure if its an issue in later versions.
> Assume a user has an application that is reading from many tables and does not have permission to read from one table.  In this case the exception does not tell them which table they can not read from.  If not familiar with the application, it can take a while to track this issue down on a system with many tables.

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