Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 18 Dec 2012 21:08:12 +0000 (UTC)
From: "John Vines (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12597603.1341502765963.25347.1355864892485@arcas>
In-Reply-To: <JIRA.12597603.1341502765963@arcas>
References: <JIRA.12597603.1341502765963@arcas>
Subject: [jira] [Commented] (ACCUMULO-670) BatchWriters do not track
 Throwables beyond Constraint Violations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

John Vines commented on ACCUMULO-670:
-------------------------------------

We track Constraint violations, we should also keep a set of the SecurityErrorCodes encountered. This will provide enough information to determine what broke. Or at least weed out a security violation from a server side error.
                
> BatchWriters do not track Throwables beyond Constraint Violations
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-670
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-670
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.4.1
>            Reporter: John Vines
>            Assignee: John Vines
>             Fix For: 1.5.0
>
>
> Working on ACCUMULO-259 and adapting the Security Random Walk test to account for cached credentials, to prevent it from crapping out on ambiguous credentials (credentials which are currently propagating). And I noticed that our client side Writers provide no means of feedback to the client if there is a non-ConstraintViolationException.
> That is, looking at the TabletServerBatchWriter specifically, we keep track of which servers had errors, which key extents had errors, and what ConstrainViolations we saw, but we don't actually track the actual Throwables we get, aside from ConstraintViolation. We should keep a Collection or Set of the Throwables we see so client code can do proper case checking as well.

--
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