[ 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-2.patch - I changed the format of the tableName in the error Messages to be <tableName>(ID:<tableId>). - I added instance to the MRE constructor - I created ACCUMULO-1144 to capture that the tableName in the ThriftScanner$ScanState is really tableId > 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-2.patch, 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