Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03E79D76D for ; Tue, 18 Dec 2012 17:50:16 +0000 (UTC) Received: (qmail 39354 invoked by uid 500); 18 Dec 2012 17:50:14 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 39289 invoked by uid 500); 18 Dec 2012 17:50:14 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 39231 invoked by uid 99); 18 Dec 2012 17:50:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 17:50:12 +0000 Date: Tue, 18 Dec 2012 17:50:12 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs updated ACCUMULO-670: --------------------------------------- Assignee: John Vines Reporter: John Vines (was: jv) > 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