[
https://issues.apache.org/jira/browse/HIVE-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766251#comment-13766251
]
Sushanth Sowmyan commented on HIVE-5112:
----------------------------------------
Compiled code for protobuf is supposed to be backward-compatible across
protobuf releases(old classes with new protobuf jar) . The only case where
protobuf backward compatibility is supposed to bite you is when you have
generated code with an old protobuf jar that you're trying to compile with a
new protobuf jar. It's supposed to cause compile-time hassles, not runtime
hassles.
So, I wanted to see if it was a difficult task upgrading hive-protobuf to a
newer protobuf as well and so, tried to check out hive-protobuf to test to see
if it was a simple update to 2.5 for that. I see only one .proto file, and it's
used by the tests. I was able to generate new code for it that compiles, but I
get test failures all over from the version of hive_test that I compiled
(return code 9 and all that)
That got me thinking - if the problem comes from a "protobuf 2.5 is not
production-certified" stance, then shouldn't hive-0.12 also not match
production-certification?
> 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
