accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1018) Client does not give informative message when user can not read table
Date Mon, 04 Feb 2013 15:00:19 GMT

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

Keith Turner commented on ACCUMULO-1018:
----------------------------------------

bq. Under what circumstances can a client not know which table it was trying to read when
it got a permissions error?

One situation is that Alice writes and application that reads from 20 tables using the scanner.
 Bob deploys Alice's application on an Accumulo instance with 100's of tables.  When the application
says it can not read something, Bob has to spend a lot of time figuring out what it can not
read.  If the scanner exception gave the table name, it would make things a lot easier for
Bob.  Sure Alice's application could have given a better error message, but it would be easy
for the scanner to do this so I do not see why it should not.
                
> 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

Mime
View raw message