[
https://issues.apache.org/jira/browse/HDFS-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068622#comment-13068622
]
Arun C Murthy commented on HDFS-2060:
-------------------------------------
Todd, the advantage of the approach in MAPREDUCE-279 is not merely pluggability
- in fact, pluggability is merely a side-benefit.
Architecturally the biggest benefit is that it provides a clean separation
between on-wire and in-memory types. I'd argue having them both be the same is
the easiest way to break compatibility, not just 'serialization' or 'protocol'
compatibility, but semantic compatibility. It's too easy to add a field and
have it show up in the server/client, thus my suggestion to separate the
on-wire and in-memory types ala MAPREDUCE-279.
Plus, this provides the added benefit of not being too tied to a particular
serialization framework's idiosyncrasies.
> DFS client RPCs using protobufs
> -------------------------------
>
> Key: HDFS-2060
> URL: https://issues.apache.org/jira/browse/HDFS-2060
> Project: Hadoop HDFS
> Issue Type: New Feature
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-2060-getblocklocations.txt
>
>
> The most important place for wire-compatibility in DFS is between clients and
> the cluster, since lockstep upgrade is very difficult and a single client may
> want to talk to multiple server versions. So, I'd like to focus this JIRA on
> making the RPCs between the DFS client and the NN/DNs wire-compatible using
> protocol buffer based serialization.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
