[
https://issues.apache.org/jira/browse/HIVE-14309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388636#comment-15388636
]
Owen O'Malley commented on HIVE-14309:
--------------------------------------
The names in org.apache.orc were internal names that were created as part of
the split from Hive. The users of Hive still use the traditional package name
of org.apache.hadoop.hive.ql.io.orc. I shouldn't have put any of the classes
into the org.apache.orc package until ORC was ready to release them, but I
screwed up. I've looked through the source code for Spark, Storm, Flume, Pig,
and Oozie and no one is using the org.apache.orc classes and they using the
original org.apache.hadoop.hive.ql.io.orc class names.
Unfortunately, Hive's users now can't use both the current ORC library and Hive
2.0.1 or Hive 2.1.0. That really sucks and will cause a lot of problems down
stream. By just renaming the packages to org.apache.hive.orc, we won't change
the functionality and the two versions of ORC will live side by side.
While the org.apache.orc package is an implementation detail from Hive's point
of view, it is the primary API for ORC. So no, moving the package in ORC
doesn't make sense.
> 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)
