[
https://issues.apache.org/jira/browse/HIVE-14309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030376#comment-16030376
]
Owen O'Malley commented on HIVE-14309:
--------------------------------------
Ok, this pull request https://github.com/apache/hive/pull/191 does:
* rename the packages in hive-orc to org.apache.hive.orc
* updates the references to the moved packages from other modules
No clients use org.apache.hive:hive-orc so this just makes the classes internal
to hive where they don't conflict if clients use both the hive and orc jars. In
hive 2.3 and later, this is unnecessary because hive uses the orc project's
artifacts.
> 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)
