Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 5 Mar 2013 15:07:13 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12630138.1359643102948.383469.1362496033721@arcas>
In-Reply-To: <JIRA.12630138.1359643102948@arcas>
References: <JIRA.12630138.1359643102948@arcas>
Subject: [jira] [Commented] (ACCUMULO-1018) Client does not give informative
 message when user can not read table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593454#comment-13593454 ] 

Keith Turner commented on ACCUMULO-1018:
----------------------------------------

I was thinking of something else.  Was thinking of the case where there are two extents E1 and E2, both from table T1.  The extents see different security errors.  So the input would be something like the following.

{noformat}
  {E1={SE1}, E2={SE2}}
{noformat}

I think the code will output the following

{noformat}
  {T1={SE2}}
{noformat}

It should output the following

{noformat}
  {T1={SE1, SE2}}
{noformat}


> 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: Kevin Faro
>             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