[
https://issues.apache.org/jira/browse/HIVE-14309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388498#comment-15388498
]
Gunther Hagleitner commented on HIVE-14309:
-------------------------------------------
Since hive used to be the only place to pick up orc it seems a bad idea to
change package names of released versions. Why can't you move the class names
out of the way in a new ORC release? As you say from 2.2+ this shouldn't be an
issue anyways.
> 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.4#6332)
