[
https://issues.apache.org/jira/browse/MAPREDUCE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047867#comment-13047867
]
Arun C Murthy commented on MAPREDUCE-279:
-----------------------------------------
Yep, it would be nice to completely mavenize and I strongly believe it should
be our goal.
Maybe we can do it in stages, have a hybrid one on day one when we merge MR-279
into trunk and then do the whole nine yards? That way each can proceed
independently. Currently it's becoming painful to manage a large branch and
hence my suggestion to get it into trunk and do mavenization independently.
Thoughts?
> Map-Reduce 2.0
> --------------
>
> Key: MAPREDUCE-279
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-279
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker, tasktracker
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Fix For: 0.23.0
>
> Attachments: MR-279.patch, MR-279.patch, MR-279.sh,
> MR-279_MR_files_to_move.txt, capacity-scheduler-dark-theme.png,
> multi-column-stable-sort-default-theme.png, yarn-state-machine.job.dot,
> yarn-state-machine.job.png, yarn-state-machine.task-attempt.dot,
> yarn-state-machine.task-attempt.png, yarn-state-machine.task.dot,
> yarn-state-machine.task.png
>
>
> Re-factor MapReduce into a generic resource scheduler and a per-job,
> user-defined component that manages the application execution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
