[ 
https://issues.apache.org/jira/browse/HIVE-14309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510407#comment-15510407
 ] 

Owen O'Malley commented on HIVE-14309:
--------------------------------------

I've had multiple users complain about this now. :(

Managing classpaths is *really* error-prone in a lot of different contexts.

None of the solutions are great, but this one makes it very clear what 
happened. We move all of classes that hive publishes out of org.apache.orc to 
orc.apache.hive.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.4#6332)

Reply via email to