[
https://issues.apache.org/jira/browse/MAPREDUCE-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13528334#comment-13528334
]
Arun C Murthy commented on MAPREDUCE-4808:
------------------------------------------
Asokan, thanks for the clarification.
However, I'm still trying to understand what you are trying to achieve here.
The original goals of the parent task (MAPREDUCE-2454) was to make 'sort
pluggable'.
We've accomplished that with MAPREDUCE-4807 and MAPREDUCE-4809.
Now, are we done? If not, what else is remaining to achieve that? Do you need
some special hook in the Reducer's merge for Syncsort?
As I've told you in person, when making sweeping changes to framework it's
better to focus on the 'goal' and make as minimal changes to get there.
We can always do more work and add more features, but let's do one thing at a
time. We can add limit-N etc. separately, it just delays this jira - why do
that?
> Allow reduce-side merge to be pluggable
> ---------------------------------------
>
> Key: MAPREDUCE-4808
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4808
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Affects Versions: 2.0.2-alpha
> Reporter: Arun C Murthy
> Assignee: Mariappan Asokan
> Fix For: 2.0.3-alpha
>
> Attachments: COMBO-mapreduce-4809-4812-4808.patch,
> mapreduce-4808.patch
>
>
> Allow reduce-side merge to be pluggable for MAPREDUCE-2454
--
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
