[
https://issues.apache.org/jira/browse/HADOOP-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641213#action_12641213
]
Owen O'Malley commented on HADOOP-4467:
---------------------------------------
Wouldn't it be better to use the class loader associated with the configuration
rather than the current thread? Basically, use
{code}
conf.getClassByName(name);
{code}
Clearly the conf for the serializer would need to be saved from the constructor.
> SerializationFactory should use current context ClassLoader
> -----------------------------------------------------------
>
> Key: HADOOP-4467
> URL: https://issues.apache.org/jira/browse/HADOOP-4467
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.18.1, 0.19.0
> Reporter: Chris K Wensel
> Attachments: hadoop-4467.patch
>
>
> SerializationFactory#add calls Class.forName without a ClassLoader instance.
> This prevents user-space Serialization classes from being loaded.
> The resulting ClassNotFoundException is eaten after being logged, and a NPE
> is thrown further down the line when a Serializer is requested.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
