[
https://issues.apache.org/jira/browse/HADOOP-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205206#comment-13205206
]
Sanjay Radia commented on HADOOP-7557:
--------------------------------------
* There is clean layering between IPC layer and RPC layer - we should retain
that.
* If the rpc engine wasn't there i would not add it. But it is there and it is
now clean. I am glad that doug added that.
** It can help us provide 20 compatibility - 20 compatibility is one of the
things that prevents FB from moving to trunk. I personally don't want to do the
work for 20 compatibility but if FB can do it for their 20 and it helps them
move to trunk this is really goodness for the community. (Dhruba and i have
discussed this issue).
** It can also help us support compatibility with HBase rpc in the future and
both projects can consider sharing RPC layer.
** If there is any future discontinuity in our RPC, the RPC Engine can help us
deal with the discontinuity.
* Another project can use Hadoop RPC but a different serialization then it
can. (Say avro or thrift).
* By adding the field I have suggested, Doug can add his k-v pair as a parallel
structure if he wishes. Indeed that field should be there anyway from good
protocol/layering principals. K-V proposal is clearly another form of
serialization and in that sense not really neutral; but as Doug argues it does
have the advantage over PB that it does not require a tool to generate it.
* I am okay with making PB the default engine and am neutral about removing
writable engine.
> Make IPC header be extensible
> -------------------------------
>
> Key: HADOOP-7557
> URL: https://issues.apache.org/jira/browse/HADOOP-7557
> Project: Hadoop Common
> Issue Type: Sub-task
> 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
