[
https://issues.apache.org/jira/browse/HIVE-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738357#comment-15738357
]
Gunther Hagleitner commented on HIVE-14007:
-------------------------------------------
[~owen.omalley] thanks for the info, but I don't understand the argument about
ORC 54. The current behavior and the fix to encode column names was shipped in
hive 2 and this patch fundamentally changes how alter table statements/schema
evolution works. You're not saying what the impact is, but I think it could be
as bad as ending up with situations where you can't read any of your data
anymore after upgrade within hive 2, right? And I don't see a fallback option
or migration path.
Resolution of this should probably be tracked in it's own blocking jira,
instead of coming in through this.
> Replace ORC module with ORC release
> -----------------------------------
>
> Key: HIVE-14007
> URL: https://issues.apache.org/jira/browse/HIVE-14007
> Project: Hive
> Issue Type: Bug
> Components: ORC
> Affects Versions: 2.2.0
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 2.2.0
>
> Attachments: HIVE-14007.patch, HIVE-14007.patch, HIVE-14007.patch,
> HIVE-14007.patch
>
>
> This completes moving the core ORC reader & writer to the ORC project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
