hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prakash (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3087) CLASSPATH not the same after MAPREDUCE-2880
Date Fri, 21 Oct 2011 15:44:32 GMT

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

Ravi Prakash commented on MAPREDUCE-3087:

Vinod! Thanks for your comment. The contents of the mrapp-generated-classpath in the test-mr-app.jar
file I uploaded are :

$ cat mrapp-generated-classpath

It does not need to be automatically generated. It is present ONLY because setMRFrameworkClasspath
looks for mrapp-generated-classpath on MRApps.java:181
bq. classpathFileStream = thisClassLoader.getResourceAsStream(mrAppGeneratedClasspathFile);

Without it, my test would throw an exception because the call above would return null. The
specific line I want to exercise (MRApps.java:192) in the unit test comes after this line.

If you have another way to structure the test, please suggest it.

OR we can check in the single line change (MRApps.java:192) which we all agree is right without
writing this test.

> CLASSPATH not the same after MAPREDUCE-2880
> -------------------------------------------
>                 Key: MAPREDUCE-3087
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3087
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Ravi Prakash
>            Assignee: Ravi Prakash
>            Priority: Critical
>             Fix For: 0.23.0
>         Attachments: MAPREDUCE-3087.patch, MAPREDUCE-3087.patch, MAPREDUCE-3087.patch,
MAPREDUCE-3087.patch, notworking.classpath.uniq, test-mr-app.jar, working.classpath.uniq
> After MAPREDUCE-2880, my classpath was missing key jar files. 

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


View raw message