hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4408) allow jobs to set a JAR that is in the distributed cached
Date Fri, 24 Aug 2012 01:41:42 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440865#comment-13440865
] 

Robert Kanter commented on MAPREDUCE-4408:
------------------------------------------

I pulled the latest changes to trunk on my machine and those tests also fail (without my patch).
 It looks like it must be one or more of these commits that's causing the failures:
{code}HADOOP-4572. Can not access user logs - Jetty is not configured by default to serve
aliases/symlinks (ahmed via tucu)
Revert HDFS-3837. Fix DataNode.recoverBlock findbugs warning.
Ammend previous commit to remove TestFileCreationNamenodeRestart.
HDFS-3715. Fix TestFileCreation#testFileCreationNamenodeRestart. Contributed by Andrew Whang{code}
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2768/changes
                
> 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
>         Attachments: MAPREDUCE-4408-branch-1.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message