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

Justin Coffey commented on HIVE-6757:
-------------------------------------

Owen, the solution your proposing means that there is no seamless upgrade path 
for existing parquet-hive users and that somewhere on the hive wiki there will 
have to be a call out "attention existing parquet users, you must include the 
parquet-hive.jar when upgrading to hive 13.  we're sorry, but this is the price 
you have to pay for being an early adopter and driving functionality".

One of the goals of the #HIVE-5783 patch was to make the lives of parquet users 
easier (there were of course many other reasons, but ease of use is a good goal 
in and of itself).  The classes as they are do no harm and it's hard to see how 
they pollute the code base of Hive in any significant way.  This patch kinda 
sorta seems a tiny bit punitive if you ask me.

Please don't take any of this the wrong way, but I believe this is what a fair 
chunk of the parquet-hive community might think if this patch is committed.

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

Reply via email to