[
https://issues.apache.org/jira/browse/HDFS-11010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576199#comment-15576199
]
Anu Engineer commented on HDFS-11010:
-------------------------------------
bq. What's the motivation for upgrading to PB 3, besides being newer?
It is more about looking at the lifetime of Hadoop 3.0. PB 2.5 was released in
2013. By the time we go to GA with 3.0 it will be 4 years old. if you assume
that Hadoop 3.0 is going to live for another 4 years, PB 2.5 would be long past
its prime or having any engineering support. Since we do have classpath
isolation would it not make sense to upgrade in this cycle ?
Let me ask the question in a different way, what about PB 3 is concerning to
you ? I am offering to do this work in a branch and prove that it works well
before we bring it in. That is more than what we do for most projects in the
trunk. Also if we find that it breaks 3.0 in ways which is not acceptable
according to our compatibility policy let us not ship this. I don't want to
work on this without getting a consensus in the community that this is
something that is acceptable.
I think we have an window of opportunity with 3.0 release, To move to a
supported tool chain. Given how critical PB is to us, I think 3.0 would be a
great place to upgrade.
> Update to Protobuf 3 in trunk
> -----------------------------
>
> Key: HDFS-11010
> URL: https://issues.apache.org/jira/browse/HDFS-11010
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 3.0.0-alpha2
> Reporter: Anu Engineer
>
> This JIRA is to propose that we should move to protobuf 3 from protobuf 2.5.
> This allows us to stay with the newer versions of the protobuf.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
