[
https://issues.apache.org/jira/browse/ACCUMULO-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567799#comment-13567799
]
Keith Turner commented on ACCUMULO-1018:
----------------------------------------
I also think the client code will have all of the information needed, its just
a matter of passing it along. Maybe some client code does, I have not really
looked into it. Just saw a case in 1.4 where the scanner was not passing this
info along. Need to look at scanner, batch scanner, batch writer, and table
operations.
> 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
