[
https://issues.apache.org/jira/browse/HIVE-14309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030386#comment-16030386
]
Alan Gates commented on HIVE-14309:
-----------------------------------
+1, as long as this is applied only to the 2.2 branch. As it just changes
import statements it seems ok.
It would be good to put a detailed comment in the orc/pom.xml explaining how
this works now, as anyone who has to maintain this later is going to be
seriously confused as to why the files have imports for org.apache.hive.orc yet
the files list their packages as org.apache.orc.
> Fix naming of classes in orc module to not conflict with standalone orc
> -----------------------------------------------------------------------
>
> Key: HIVE-14309
> URL: https://issues.apache.org/jira/browse/HIVE-14309
> Project: Hive
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
> The current Hive 2.0 and 2.1 releases have classes in the org.apache.orc
> namespace that clash with the ORC project's classes. From Hive 2.2 onward,
> the classes will only be on ORC, but we'll reduce the problems of classpath
> issues if we rename the classes to org.apache.hive.orc.
> I've looked at a set of projects (pig, spark, oozie, flume, & storm) and
> can't find any uses of Hive's versions of the org.apache.orc classes, so I
> believe this is a safe change that will reduce the integration problems down
> stream.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
