You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Lefty Leverenz (JIRA)" <ji...@apache.org> on 2017/06/13 05:25:02 UTC

[jira] [Commented] (HIVE-14309) Fix naming of classes in orc module to not conflict with standalone orc

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

Lefty Leverenz commented on HIVE-14309:
---------------------------------------

[~owen.omalley], you committed this to branch-2.2 on May 31, so please update the status and fix version.

See commit fd1188a6a79c6da868d463c1e5db50c017c3b1a2.

> 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.4.14#64029)