[
https://issues.apache.org/jira/browse/HIVE-14309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390391#comment-15390391
]
Gunther Hagleitner commented on HIVE-14309:
-------------------------------------------
I've looked at the classes that would be impacted. If I'm not mistaken you're
talking about 100 classes which are pretty much all of ORC. 70 of those are
non-test classes. Since hive used to be until very recently the only source of
orc I also don't see a way to guarantee that no one else is using these classes
and wouldn't be affected by changing this on released lines going back over 6
months.
I also get that you don't want to change those in ORC upstream now. That would
mean you have to move a lot of stuff out of the way.
As a consequence I think the best thing to do is nothing for 2.0 and 2.1. If
someone wants to use ORC with hive on the classpath in those versions they
should probably just use the hive classes. Starting with hive 2.2 they will be
able to switch to ORC proper. If they absolutely must suck in the new ORC
project they should probably shade it in their code for the time being. That
also will get them over the hump.
> 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)
