[
https://issues.apache.org/jira/browse/MAPREDUCE-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated MAPREDUCE-4408:
-------------------------------------------
Fix Version/s: 0.23.4
I pulled this into branch-0.23 too.
> allow jobs to set a JAR that is in the distributed cached
> ---------------------------------------------------------
>
> Key: MAPREDUCE-4408
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4408
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv1, mrv2
> Affects Versions: 1.0.3, 2.0.0-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Robert Kanter
> Fix For: 1.2.0, 2.0.2-alpha, 0.23.4
>
> Attachments: MAPREDUCE-4408-branch-1.patch, MAPREDUCE-4408.patch,
> MAPREDUCE-4408.patch
>
>
> Setting a job JAR with JobConf.setJar(String) and Job.setJar(String) assumes
> that the JAR is local to the client submitting the job, thus it triggers
> copying the JAR to HDFS and injecting it to the distributed cached.
> AFAIK, this is the only way to use uber JARs (JARs with JARs inside) in MR
> jobs.
> For jobs launched by Oozie, all JARs are already in HDFS. In order for Oozie
> to suport uber JARs (OOZIE-654) there should be a way for specifying as JAR a
> JAR that is already in HDFS.
--
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
