[
https://issues.apache.org/jira/browse/ACCUMULO-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586457#comment-13586457
]
Hudson commented on ACCUMULO-670:
---------------------------------
Integrated in Accumulo-Trunk-Hadoop-2.0 #102 (See
[https://builds.apache.org/job/Accumulo-Trunk-Hadoop-2.0/102/])
ACCUMULO-670 ACCUMULO-765 - merging 1449793 to trunk. Plus a little extra,
it looks like? (Revision 1449794)
Result = FAILURE
vines :
Files :
* /accumulo/trunk
* /accumulo/trunk/core
*
/accumulo/trunk/core/src/main/java/org/apache/accumulo/core/client/MutationsRejectedException.java
*
/accumulo/trunk/core/src/main/java/org/apache/accumulo/core/client/mapred/AccumuloOutputFormat.java
*
/accumulo/trunk/core/src/main/java/org/apache/accumulo/core/client/mapreduce/AccumuloOutputFormat.java
*
/accumulo/trunk/core/src/main/java/org/apache/accumulo/core/util/shell/commands/InsertCommand.java
* /accumulo/trunk/examples
*
/accumulo/trunk/examples/simple/src/main/java/org/apache/accumulo/examples/simple/client/RandomBatchWriter.java
* /accumulo/trunk/test/src/main/java/org/apache/accumulo/test/TestIngest.java
*
/accumulo/trunk/test/src/main/java/org/apache/accumulo/test/functional/PermissionsTest.java
> 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
