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

Hadoop QA commented on MAPREDUCE-4740:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12550309/MR-4740.txt
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2956//console

This message is automatically generated.
                
> only .jars can be added to the Distributed Cache classpath
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-4740
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4740
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.3, 2.0.2-alpha
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Blocker
>         Attachments: MR-4740.txt, MR-4740.txt
>
>
> Koji tracked down this one.
> {noformat}
> $ cat mycat.sh
> #!/bin/sh
> cat >& /dev/null
> $JAVA_HOME/bin/jinfo $PPID | grep java.class.path
> export | grep CLASSPATH
> ls -l 
> $ myfile=/user/me/myclasses.zip; yarn jar
> hadoop-streaming.jar
> -Dmapreduce.job.cache.archives=hdfs:///${myfile}
> -Dmapreduce.job.classpath.archives=${myfile} -input in.txt -output out 
> -reducer NONE -mapper mycat.sh  -file mycat.sh
> {noformat}
> So, cachearchive like class.zip or class.tar.gz were never set as part of the
> classpath even though they were properly set by 
> DistributedCache.addArchiveToClassPath.
> It looks like we are parsing the classpath out of the configs, but then 
> throwing that away.  It looks simple enough to add them in the correct place.

--
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

Reply via email to