[ http://issues.apache.org/jira/browse/HADOOP-419?page=all ]
Owen O'Malley updated HADOOP-419:
---------------------------------
Attachment: classloader-2.patch
ok, after chatting with doug, here is a different version.
It leaves the class loader in the Configuration, but it exposes a
getClassByName method that allows a class lookup by class name rather than by
attribute name.
If the thread does not have a class loader, it will use the default, which
fixes the precise bug that Christian was hitting.
It also pulls all of the other places that were using the thread's class loader
to find classes into the same code, based on the config. Note that some of the
writeObject methods needed to have their signatures changed to pass in the
config object so that it was clear what class loader should be used.
> 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-2.patch, 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
