accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Faro (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1018) Client does not give informative message when user can not read table
Date Tue, 26 Feb 2013 16:22:13 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kevin Faro updated ACCUMULO-1018:
---------------------------------

    Attachment: ACCUMULO-1018.patch

Here is what I have so far.  There are things to clean up to make the code look a little nicer
... but I still haven't been able to crack the nut of getting tableNames from KeyExtent ...
                
> 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
>
>         Attachments: ACCUMULO-1018.patch
>
>
> 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