[
http://issues.apache.org/jira/browse/HADOOP-419?page=comments#action_12431053 ]
Doug Cutting commented on HADOOP-419:
-------------------------------------
Previously different configurations and threads were permitted to use different
classloaders. After this patch, all use the same classloader. I'm not sure
that's always right. Ideally, shouldn't Configuration.getResource() and
Configuration.getClass("foo.class") be able to refer to configuration-specific
resources, like the job jar?
> libdfs doesn't work with application threads
> --------------------------------------------
>
> Key: HADOOP-419
> URL: http://issues.apache.org/jira/browse/HADOOP-419
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/streaming
> Affects Versions: 0.5.0
> Reporter: Christian Kunz
> Assigned To: Owen O'Malley
> Fix For: 0.6.0
>
> Attachments: classloader.patch
>
>
> Using libdfs from C++ using threads I get a null pointer for the
> ThreadClassLoader, which throws an exception.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
