[
https://issues.apache.org/jira/browse/HADOOP-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002183#comment-14002183
]
Vinod Kumar Vavilapalli commented on HADOOP-10474:
--------------------------------------------------
I'll start an email thread on common-dev. My opinion is to not remove the
deprecated stuff in any of the minor releases. We got bit in the past with
users continuing to use deprecated APIs. For strictly private APIs it may make
sense, but otherwise, I think we should defer deletion of deprecated APIs to
the next major release.
Regarding the current issue, +1 to Jason's proposal of reverting both the
move/delete patches from branch-2.
> Move o.a.h.record to hadoop-streaming
> -------------------------------------
>
> Key: HADOOP-10474
> URL: https://issues.apache.org/jira/browse/HADOOP-10474
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Fix For: 2.5.0
>
> Attachments: HADOOP-10474.000.patch, HADOOP-10474.001.patch,
> HADOOP-10474.002.patch
>
>
> The classes in o.a.h.record have been deprecated for more than a year and a
> half. They should be removed. As the first step, the jira moves all these
> classes into the hadoop-streaming project, which is the only user of these
> classes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
