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, 25 Jan 2013 00:09:15 GMT


Hudson commented on ACCUMULO-955:

Integrated in Accumulo-Trunk #665 (See [])
    ACCUMULO-984 Prevent unexpected behavior when using a really small timeout values, that
get truncated to zero on conversion internally.
ACCUMULO-955 Removed the minimum value for maxMemory, and accept any non-negative value. (Revision

     Result = SUCCESS
ctubbsii : 
Files : 
* /accumulo/trunk/core/src/main/java/org/apache/accumulo/core/client/
* /accumulo/trunk/core/src/test/java/org/apache/accumulo/core/client/

> 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