You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2008/03/07 07:39:03 UTC
[jira] Resolved: (HADOOP-2959) When a mapper needs to run a
combiner, it should create one and reuse it, instead of creating one per
partition per spill
[ https://issues.apache.org/jira/browse/HADOOP-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley resolved HADOOP-2959.
-----------------------------------
Resolution: Won't Fix
This is a feature, not a bug. The reduce (and combiner) are guaranteed they will get the inputs in sorted order. If you re-use a combiner, that is no longer true. If initialization is expensive, move it to an external/static class.
> When a mapper needs to run a combiner, it should create one and reuse it, instead of creating one per partition per spill
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-2959
> URL: https://issues.apache.org/jira/browse/HADOOP-2959
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.16.0
> Reporter: Runping Qi
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.