[
https://issues.apache.org/jira/browse/HIVE-14007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738471#comment-15738471
]
Gunther Hagleitner commented on HIVE-14007:
-------------------------------------------
The other thing I think we need community wide clarity on before you rip out
orc is how we’re going to keep developing hive afterwards. Right now there’s a
cyclic dependency. Hive -> ORC -> Hive - because of a shared storage api.
There are features that touch all three. And it turns out these are more
frequent than expected. Examples: HIVE-15335 ([~mmccline]), HIVE-14453
([~sershe]), HIVE-15269 ([~jdere]). I’m sure there there are more given how
vectorization, llap and acid are interlinked.
How do you propose to handle development and release of these features given
the cyclic dependency? How do you work out feature branches/ snapshots?
If a successful feature commit requires sequential hive and orc releases, then
that means minimum several months before commit and that's not great. How will
this be done?
Side note: None of the features above actually change the actual format (bits
on disk), so maybe you’re just removing too much.
Final concern: Looking over the PMC and committer lists in ORC it looks like
many people working on ACID, vectorization or llap will lose the ability to do
what they are doing today with this change. I don't think we should move ahead
w/o closing this gap.
> 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)
