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

Steve Loughran commented on HADOOP-13363:
-----------------------------------------

protoc 2.4 is actually becoming hard to find: homebrew doesn't serve it up any 
more, making setting up new dev systems hard.

At the same time, not only does proto3 appear to have wire changes. *I have no 
faith whatsoever in point releases of protobuf being compatible with previous 
protoc-generated coded code*. To be fair, Avro has a similar policy. They just 
appear to recognise that the "just rebuild everything" strategy doesn't work 
for us. That is: the ASF big data stack is distributed development system, 
whereas the google build is centralised.

If PB can be shaded, then moving up would be good, and, with the shading, let 
us update at our own rate.



> 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
>         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
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to