[
https://issues.apache.org/jira/browse/HIVE-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743156#comment-15743156
]
Gunther Hagleitner commented on HIVE-14007:
-------------------------------------------
[~owen.omalley] this partially addresses my concerns but you're being vague
about what exactly and when. So I will try to be clear. I'm -1 on this.
Blockers for me are:
a) change breaks compatibility. (schema evolution)
b) there's no documented and proven way to actually be able to turn these
features/bugs around in 3 days. (many open questions, what's considered public
v private, backwards compat criteria of the api, documentation for api itself,
documentation of release mechanics, what are the version numbers, who votes on
it, do a feature end to end to demonstrate.)
c) not sure why it's up to you who gets to play and who doesn't. for me at the
very least anyone who's been working on ACID, ORC, LLAP, cloud/s3 or
vectorization should keep their committership/pmc in ORC (or have it
transferred/added). i'm fine if folks explicitly opt out of that.
given how these things are interrelated, anything else will just make it
harder/impossible for hive devs to do their work.
> 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)
