hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-5112) Upgrade protobuf to 2.5 from 2.4
Date Fri, 13 Sep 2013 07:09:53 GMT

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

Thejas M Nair commented on HIVE-5112:
-------------------------------------

There are discussions in the hadoop mailing lists about having the hadoop 2 GA in few weeks.
So I think it is worthwhile that we aim to have 0.12 to be compatible with the hadoop 2 line
as well.

[~appodictic] I don't think your -1 is reasonable for the following reasons- 
- I don't consider it feasible to stop upgrading jars in hive because the old version of jar
was used by some udf/serde/inputformat. (But I do think that in long term we need to explore
ways of isolating the hive jars/classes vs user jars/classes) 
- In the example you cited, as Sushanth mentioned, you don't need to make any code changes
to use protobuf 2.5. I suspect most users who are using protobuf with dynamic schema would
not choose to work with generated code. So the number of users this is likely to affect is
small.
- The upgrade is inevitable. With it being in trunk, it is in its way into the 0.13 release.

I request you to please reconsider your -1. 

                
> Upgrade protobuf to 2.5 from 2.4
> --------------------------------
>
>                 Key: HIVE-5112
>                 URL: https://issues.apache.org/jira/browse/HIVE-5112
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Brock Noland
>            Assignee: Owen O'Malley
>             Fix For: 0.13.0
>
>         Attachments: HIVE-5112.2.patch, HIVE-5112.D12429.1.patch
>
>
> Hadoop and Hbase have both upgraded protobuf. We should as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message