[
https://issues.apache.org/jira/browse/MAPREDUCE-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690560#comment-13690560
]
Karthik Kambatla commented on MAPREDUCE-5221:
---------------------------------------------
[~ozawa], I thought all of MAPREDUCE-5221, MAPREDUCE-5294 and MAPREDUCE-5295
are related and motivated by the same bug (from the description) that
reduce-side combiner is not called using the new API. Or, did I miss any other
motivation for the other two JIRAs?
IIUC, we could just use an if condition similar to the one in my previous
comment, and that should solve the issue and we don't need the other two JIRAs.
No? Am I missing something?
> Reduce side Combiner is not used when using the new API
> -------------------------------------------------------
>
> Key: MAPREDUCE-5221
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5221
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.0.4-alpha
> Reporter: Siddharth Seth
> Assignee: Tsuyoshi OZAWA
> Attachments: MAPREDUCE-5221.1.patch, MAPREDUCE-5221.2.patch,
> MAPREDUCE-5221.3.patch, MAPREDUCE-5221.4.patch
>
>
> If a combiner is specified using o.a.h.mapreduce.Job.setCombinerClass - this
> will silently ignored on the reduce side since the reduce side usage is only
> aware of the old api combiner.
> This doesn't fail the job - since the new combiner key does not deprecate the
> old key.
--
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
