[
https://issues.apache.org/jira/browse/HADOOP-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860590#action_12860590
]
Chris Douglas commented on HADOOP-6698:
---------------------------------------
bq. 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.
HADOOP-6420 was completed with MAPREDUCE-1126 as a use case, but it's an
independent feature. Does it need to be backed out? Also, HADOOP-6438 was
closed as invalid, not committed, so fortunately there's nothing to be backed
out, there.
> 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
>
> Attachments: HADOOP-6698.patch, HADOOP-6698.patch
>
>
> 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.
