hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Peña (JIRA) <j...@apache.org>
Subject [jira] [Commented] (HIVE-14309) Fix naming of classes in orc module to not conflict with standalone orc
Date Sun, 20 Nov 2016 17:31:58 GMT

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

Sergio Peña commented on HIVE-14309:
------------------------------------

I'm moving this JIRA out of 2.1.1 release as it is not a blocker nor critical for a 2.1.1
RC version. Feel free to commit it to branch 2.1 if the patch is ready before the release.

> 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)

Mime
View raw message