accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (ACCUMULO-955) Update MapReduce API to match the changes in ACCUMULO-706
Date Thu, 24 Jan 2013 01:30:11 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher Tubbs reopened ACCUMULO-955:
----------------------------------------


As part of this fix, a minimum, "reasonable" value of 1k was added to maxMemory, but it shouldn't
be there. Any non-negative value is valid... even values less than the size of a single mutation,
which should just cause the batchwriter to flush immediately. This change needs to be reverted,
and documentation added to explain this.
                
> Update MapReduce API to match the changes in ACCUMULO-706
> ---------------------------------------------------------
>
>                 Key: ACCUMULO-955
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-955
>             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: http://www.atlassian.com/software/jira

Mime
View raw message