accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-955) Update MapReduce API to match the changes in ACCUMULO-706
Date Fri, 18 Jan 2013 04:08:13 GMT


Hudson commented on ACCUMULO-955:

Integrated in Accumulo-Trunk-Hadoop-2.0 #5 (See [])
    ACCUMULO-955 Made BatchWriterConfig Writable, so it can be stored in a job's configuration
in a human-readable way. Updated AccumuloOutputFormat to use it, and
added unit tests for ACCUMULO-706 and ACCUMULO-955. Added an additional check for a reasonable
minimum maxMemory value. (Revision 1435013)

     Result = FAILURE
ctubbsii : 
Files : 
* /accumulo/trunk/core/src/main/java/org/apache/accumulo/core/client/
* /accumulo/trunk/core/src/main/java/org/apache/accumulo/core/client/mapreduce/
* /accumulo/trunk/core/src/main/java/org/apache/accumulo/core/util/shell/commands/
* /accumulo/trunk/core/src/main/java/org/apache/accumulo/core/util/shell/commands/
* /accumulo/trunk/core/src/test/java/org/apache/accumulo/core/client/
* /accumulo/trunk/core/src/test/java/org/apache/accumulo/core/client/mapreduce/
* /accumulo/trunk/examples/simple/src/main/java/org/apache/accumulo/examples/simple/mapreduce/
* /accumulo/trunk/server/src/main/java/org/apache/accumulo/server/test/continuous/

> Update MapReduce API to match the changes in ACCUMULO-706
> ---------------------------------------------------------
>                 Key: ACCUMULO-955
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.5.0
> This change should be similar to how the MapReduce API changed for IteratorSetting. Specifically,
if we make BatchWriterConfig implement Writable, we can store it in the Job's configuration
pretty easily, and it would carry the same benefits as the switch to using BatchWriterConfig
in the Connector API.

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