[
https://issues.apache.org/jira/browse/HIVE-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951499#comment-13951499
]
Harish Butani commented on HIVE-6757:
-------------------------------------
Hi Justin, Brock,
Couple of questions/thoughts:
1.
What if we include the parquet-hive.jar in the hive-exec shaded jar? Does this
mitigate the upgrade issues for existing users?
2.
If they choose to how will existing users migrate to the new classes? Do we
provide metadata upgrade scripts? Do we have to support their existing sql
code: for e.g. we add checks in the hive parsing layer to replace old parquet
class references with new classes.
So the migration process when we remove(now or in the future) the deprecated
classes is not clear. Can you guys please help me understand how this will play
out.
> Remove deprecated parquet classes from outside of org.apache package
> --------------------------------------------------------------------
>
> Key: HIVE-6757
> URL: https://issues.apache.org/jira/browse/HIVE-6757
> Project: Hive
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Priority: Blocker
> Fix For: 0.13.0
>
> Attachments: HIVE-6757.patch, parquet-hive.patch
>
>
> Apache shouldn't release projects with files outside of the org.apache
> namespace.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
