hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-9424) The "hadoop jar" invocation should include the passed jar on the classpath as a whole
Date Thu, 21 Mar 2013 09:47:15 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Harsh J updated HADOOP-9424:
----------------------------

    Attachment: HADOOP-9424.patch

Attached patch adds the passed jar (the argument) to CLASSPATH before RunJar is invoked. This
solves the {{HADOOP_CLASSPATH=Y.jar hadoop jar X.jar Main}} failing case described above.

Another workaround would of course be to manually add such a jar to HADOOP_CLASSPATH, such
as {{HADOOP_CLASSPATH=X.jar:Y.jar hadoop jar X.jar Main}} but remembering to do that is annoyingly
painful when it can be fixed without issues.
                
> The "hadoop jar" invocation should include the passed jar on the classpath as a whole
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9424
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9424
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 2.0.3-alpha
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Minor
>         Attachments: HADOOP-9424.patch
>
>
> When you have a case such as this:
> {{X.jar -> Classes = Main, Foo}}
> {{Y.jar -> Classes = Bar}}
> With implementation details such as:
> * Main references Bar and invokes a public, static method on it.
> * Bar does a class lookup to find Foo (Class.forName("Foo")).
> Then when you do a {{HADOOP_CLASSPATH=Y.jar hadoop jar X.jar Main}}, the Bar's method
fails with a ClassNotFound exception cause of the way RunJar runs.
> RunJar extracts the passed jar and includes its contents on the ClassLoader of its current
thread but the {{Class.forName(…)}} call from another class does not check that class loader
and hence cannot find the class as its not on any classpath it is aware of.
> The script of "hadoop jar" should ideally include the passed jar argument to the CLASSPATH
before RunJar is invoked, for this above case to pass.

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

Mime
View raw message