[
https://issues.apache.org/jira/browse/ACCUMULO-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579471#comment-13579471
]
Kevin Faro commented on ACCUMULO-1018:
--------------------------------------
I started taking a look at this. It wasn't too bad to add support for
scanning. I added an optional tableName field to AccumuloSecurityException
that the ThriftScanner sets the tableName before it re-throws the excpetion.
TableOperations and BatchScanner was similar.
However, the (MultiTable)BatchWriter throws a MutationsRejectedException that
has the KeyExtent->ErrorCode pairings (as John pointed out) but I do not see an
effective way map KeyExtent.tableId to a tableName (that the client would
probably prefer) since the MRE doesn't have access to the instance. Any ideas?
> 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
