[
https://issues.apache.org/jira/browse/HADOOP-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126075#comment-13126075
]
Todd Lipcon commented on HADOOP-7557:
-------------------------------------
To be honest, all of this pluggability in serializations seems to be counter to
the goal of interoperability here. If we just use protobufs everywhere, than
anyone can come along in any reasonably common language and get a working
implementation of Hadoop RPC on either the server or client side. If every
single piece has a flag indicating whether it might be protobuf, avro,
Writable, msgpack, JSON, etc, then anyone trying to implement the protocol will
be faced with an insurmountable amount of work.
Making the protocol entirely generalizable smacks of REST to me- people talk
about REST as if you could have a "REST client", when in fact it's not general
at all. Do we really want Hadoop RPC to evolve to the point where I can have a
Hadoop RPC client that only understands Avro, and you can have a server that
only understands Protobuf, and we can't talk to each other despite both
"implementing Hadoop RPC"?
> Make IPC header be extensible
> -------------------------------
>
> Key: HADOOP-7557
> URL: https://issues.apache.org/jira/browse/HADOOP-7557
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
> Attachments: HADOOP-7557.patch, IpcHeader.proto, ipcHeader1.patch,
> ipcHeader2.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
