[
https://issues.apache.org/jira/browse/HADOOP-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001956#comment-14001956
]
Jason Lowe commented on HADOOP-10474:
-------------------------------------
bq. What is the effort of fixing it in Hive directly?
I'm not sure what it takes to fix it in Hive. I'm more worried about the
possibility of breaking existing deployments of Hive or other things that could
be using these given that they weren't deprecated in 1.x and would be gone in
2.5. The problem with moving them to hadoop-streaming is that jar isn't in the
default classpath in 2.x.
bq. It does not look that this patch can be directly reverted. Is it easier if
we revert HADOOP-10485 (which actually deletes the classes) in branch-2?
I propose we revert both HADOOP-10485 and this for branch-2 so all of the
records are there and in the default classpath as they were back in 1.x.
> 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)
