Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <31005405.1187730630684.JavaMail.jira@brutus>
Date: Tue, 21 Aug 2007 14:10:30 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1601) GenericWritable should use
 ReflectionUtils.newInstance to avoid problems with classloaders
In-Reply-To: <13185558.1184259845845.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521592 ] 

Doug Cutting commented on HADOOP-1601:
--------------------------------------

You've also patched UpgradeUtilities to sort directories.  This makes good sense, but is it really related to this issue, or should it rather be a separate issue?

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