[
https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880326#comment-16880326
]
Steve Loughran commented on HADOOP-13363:
-----------------------------------------
[~Kevin_Zheng] please look at the history of this JIRA and its related-to
issues. "The great Protobuf upgrade" was the most traumatic event in Hadoop
maintenance history, and while we want to move off 2.5, we are scared of what
breaks (esssentially: every class compiled with the v2.4 protoc).
We aren't going to do this just to get things working on Arm64 builds. What you
should be able to do is do builds with the -D settings to switch to a later
version. Your entire stack will need to be built with the same version, but it
should be enough for testing. And protobuf gives you the wire compatibility;
its the generated java classes which have problems
> Upgrade protobuf from 2.5.0 to something newer
> ----------------------------------------------
>
> Key: HADOOP-13363
> URL: https://issues.apache.org/jira/browse/HADOOP-13363
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.0.0-alpha1, 3.0.0-alpha2
> Reporter: Allen Wittenauer
> Assignee: Tsuyoshi Ozawa
> Priority: Major
> Labels: security
> Attachments: HADOOP-13363.001.patch, HADOOP-13363.002.patch,
> HADOOP-13363.003.patch, HADOOP-13363.004.patch, HADOOP-13363.005.patch
>
>
> Standard protobuf 2.5.0 does not work properly on many platforms. (See, for
> example, https://gist.github.com/BennettSmith/7111094 ). In order for us to
> avoid crazy work arounds in the build environment and the fact that 2.5.0 is
> starting to slowly disappear as a standard install-able package for even
> Linux/x86, we need to either upgrade or self bundle or something else.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]