accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1018) Client does not give informative message when user can not read table
Date Fri, 01 Mar 2013 22:23:13 GMT


Keith Turner commented on ACCUMULO-1018:

MRE is only constructed by the TSBW (TabletServerBatchWriter).  The TSBW could pass its Instance
to the MRE constructor.  Then MRE could use that Instance when calling methods on o.a.a.c.c.i.Tables.

If you are interested, the following changes would be nice :

 * Make the format() function you added to MRE reduce Map<KeyExtent,Set<SecurityErrorCode>>
to Map<TableNameIdString, Set<SecurityErrorCode>> and print that out.   That would
be much easier for a human to read.  If someone is interested in the details they can call
 * I am not sure all of the messages you added will have both table id and table name. Something
like "tablename(tableid)" for all the messages would be nice.
 * I believe the scanState.tableName in thrift scanner is misnamed, I think that is actually
a tableId.

> Client does not give informative message when user can not read table
> ---------------------------------------------------------------------
>                 Key: ACCUMULO-1018
>                 URL:
>             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:

View raw message