[
https://issues.apache.org/jira/browse/HDFS-11010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576699#comment-15576699
]
Anu Engineer commented on HDFS-11010:
-------------------------------------
[~chris.douglas] Thanks for the explanation. I was aware of the issue with
defaults. I was hoping that between DFSClient and HDFS server code we would be
able to fix the issue. That is why I was proposing a branch. I am expecting
that our clients will have to move to using new DFSclient since we have broken
so many of those classes already.
Let us take a step back, how do you propose that we solve this issue ?
I see 4 options:
# Bite the bullet and upgrade to proto 3 now, along with side by side
deployment of protobuf 2 based code and slowly deprecate protobuf 2.
# Fork protobuf 2 code and maintain it ourselves.
# use something new or better write our own serialization layer -- same
issues as you pointed out about breaking the world exists.
# Be forever stuck in protobuf 2.
All of them have the negatives, but I think in the "scale of evil" option 1 or
2 seems to be a better option than 3 and 4.
> 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: [email protected]
For additional commands, e-mail: [email protected]
