hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Capriolo <>
Subject Re: [jira] [Created] (HIVE-5112) Upgrade protobuf to 2.5 from 2.4
Date Fri, 13 Sep 2013 04:35:14 GMT
In conviencing current users to make developers happy of beta software
happy is not a big win. Protobuf 2.4 has been the standard for a long time
now. We and others have considerable amount of udfs that amd other things
that need to be rebuilt.

Forcing 12 to protobuf 2.5 will make it harder for me and others to
upgrade. Really this dep should all be external to hive. There is no reason
that a input or storage handler has to dictate the version of things.

I do not see what the problem of waitng 3 month is. On one hand we are
going to run 2x tests of hcat for 2 releases to guarentee comparability.

On the otherhand we are willimlng to force people to rebuild the kits to be
in sync with non release software,
On Thursday, September 12, 2013, Sushanth Sowmyan (JIRA) <>
>     []
> Sushanth Sowmyan commented on HIVE-5112:
> ----------------------------------------
> I'd also much rather have this in 0.12. Without this in 0.12, we either
block HIVE-4388 inclusion in 0.12, or require two versions of HIVE-4388,
one with protobuf 2.4 and one with 2.5. And that jira blocks being able to
work with hbase 0.96, which is in an RC stage, and past beta.
> The term beta, imo, is not so much about experimentation nowadays as it
is about being a preview.
>> Upgrade protobuf to 2.5 from 2.4
>> --------------------------------
>>                 Key: HIVE-5112
>>                 URL:
>>             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
> For more information on JIRA, see:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message