Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <32185445.1186400879383.JavaMail.jira@brutus>
Date: Mon, 6 Aug 2007 04:47:59 -0700 (PDT)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (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:all-tabpanel ]

Enis Soztutar updated HADOOP-1601:
----------------------------------

    Attachment: genericWritable_v1.1.patch

Attaching the patch, which was attached to hadoop-dev previously. 
This version compares classes, rather than class names, adds some javadoc and improves logging in the test case.

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