Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <10828799.125911271888452063.JavaMail.jira@thor>
Date: Wed, 21 Apr 2010 18:20:52 -0400 (EDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6698) Revert the io.serialization package
 to 0.20.2's api
In-Reply-To: <21261745.7641270969841016.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859555#action_12859555 ] 

Doug Cutting commented on HADOOP-6698:
--------------------------------------

This issue is fundamentally about backing out changes related to HADOOP-1126, since you've rejected that patch.  In that light, HADOOP-6420, HADOOP-6438 and HADOOP-6443 should perhaps also be backed out.

> Revert the io.serialization package to 0.20.2's api
> ---------------------------------------------------
>
>                 Key: HADOOP-6698
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6698
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: io
>            Reporter: Owen O'Malley
>            Priority: Blocker
>             Fix For: 0.21.0
>
>
> I have a lot of concern about the usability of the new generic serialization framework. Toward that end, I've filed a jira for improving it. There is resistance to pushing a new API into 0.21 at the last moment, so we should back out the changes rather than introducing a new api in 0.21 and deprecating it in 0.22.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.