[
https://issues.apache.org/jira/browse/MAPREDUCE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997614#comment-12997614
]
eric baldeschwieler commented on MAPREDUCE-279:
-----------------------------------------------
Hi Jeff,
A couple of thoughts:
1) Discussions on how to reorganize the hadoop universe probably should be
moved from this bug to their own thread. Can we restrict this thread to
discussions about the design and implementation of this work? Feel free to
start this discussion on general or in JIRA.
2) I agree with you that it is important that we structure hadoop so that it is
easy to plugin and use other technologies and I would welcome your contribution
of code to help make that a reality in this case.
3) My experience with the project split has been very negative. It is becoming
much harder, not easier to evolve the hadoop code base. Hence nigel's
suggestions (which I support) to actually move the projects closer together.
Since map-reduce is the core of Hadoop, I think it is import that Hadoop remain
able to deliver the worlds best MR solution within the project.
4) We consider this work a natural evolution of the MR project. Please don't
refer to it as Yahoo! cluster manager. That will just confuse the discussion.
The intent is to complete this work in apache and others are more then welcome
to help us with it.
Thanks,
E14
> 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
>
>
> 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
