[
https://issues.apache.org/jira/browse/MAPREDUCE-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773326#comment-13773326
]
Hitesh Shah commented on MAPREDUCE-4421:
----------------------------------------
[~jlowe] Thanks for the detailed answers to my queries.
I believe this initial patch is a good start to making MR a user-land library.
As it stands, it provides the additional flexibility which can be used by
anyone to deploy MR with either the full tarball or a mix-match approach.
Though it might be good to have some documentation on the 2 possible approaches
( full tarball vs MR tarball ) and explain how the classpath should be setup.
Depending on your viewpoint, the classpath-to-hdfs path mapping - whether it
comes in from an additional file on HDFS could be considered in a follow-up
jira if others believe this is a better solution.
The one thing to change in the patch is the documentation for
mapreduce.application.framework.path - it does not mention the use of the URI
fragment and how that interacts with the configured classpath.
Could you file a follow-up jira for the config handling?
> Remove dependency on deployed MR jars
> -------------------------------------
>
> Key: MAPREDUCE-4421
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4421
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 2.0.0-alpha
> Reporter: Arun C Murthy
> Assignee: Jason Lowe
> Attachments: MAPREDUCE-4421.patch, MAPREDUCE-4421.patch
>
>
> Currently MR AM depends on MR jars being deployed on all nodes via implicit
> dependency on YARN_APPLICATION_CLASSPATH.
> We should stop adding mapreduce jars to YARN_APPLICATION_CLASSPATH and,
> probably, just rely on adding a shaded MR jar along with job.jar to the
> dist-cache.
--
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
