You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/07/07 01:55:34 UTC

[jira] [Created] (MAPREDUCE-4408) allow jobs to set a JAR that is in the distributed cached

Alejandro Abdelnur created MAPREDUCE-4408:
---------------------------------------------

             Summary: 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: 2.0.0-alpha, 1.0.3
            Reporter: Alejandro Abdelnur
            Assignee: Alejandro Abdelnur


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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira