[
https://issues.apache.org/jira/browse/HADOOP-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521688
]
enis edited comment on HADOOP-1601 at 8/21/07 10:39 PM:
-----------------------------------------------------------------
version 1.2 of the patch with the sortFiles patch was an experiment with Raghu,
to see if the failure could be corrected by the patch in HADOOP-1696. I thought
we have made it clear in comments in HADOOP-1696, sorry for the extra noise.
Now that we saw it is, we can commit patch version 1.1(same as v1.2 w/o
sortFiles patch), after HADOOP-1749.
was (Author: enis):
version 1.2 of the patch with the sortFiles patch was an experiment with
Raghu, to see if the failure could be corrected by the patch in HADOOP-1696. I
thought we have made it clear in comments in HADOOP-1696, sorry for the extra
noise. Now that we saw it is, we can commit patch version 1.1(same as v1.2 w/o
sortFiles patch), after HADOOP-1729.
> GenericWritable should use ReflectionUtils.newInstance to avoid problems with
> classloaders
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-1601
> URL: https://issues.apache.org/jira/browse/HADOOP-1601
> Project: Hadoop
> Issue Type: Bug
> Components: io
> Affects Versions: 0.15.0
> Reporter: Owen O'Malley
> Assignee: Enis Soztutar
> Fix For: 0.15.0
>
> Attachments: genericWritable_v1.0.patch, genericWritable_v1.1.patch,
> genericWritable_v1.2-sortFiles.patch
>
>
> GenericWritable currently uses Class.newInstance and it should use
> hadoop.utils.ReflectionUtils.newInstance. Furthermore, GenericWritable should
> be Configurable and should configure the nested objects. This will prevent a
> lot of classloader issues and allow the objects to get a configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
