[
https://issues.apache.org/jira/browse/HADOOP-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204167#comment-13204167
]
Sanjay Radia commented on HADOOP-7557:
--------------------------------------
For a very long time our header have been writable and we have been supported
rpc engine - clearly the headers are not neutral to all serializations. Anyone
wanting to use PB has to be prepared to write the headers in writable. Hence
for a very long time
our implementation favored writables. If the notion of RpcEngine made sense in
current trunk why does it not make sense with PB.
We are now proposing making the headers extensible using PB.
You have proposed another solution of k-value pairs - this also makes the
headers extensible. We will have to add notions of
which keys are required and which are optional to make this work well and will
be reinventing some of the PB technology.
The machinery you are proposing is not all that simple once you fill in all the
necessary details.
I am arguing that it is perfectly okay for the headers to pick one form of
serialization that is extensible.
We can supply a small c-or-java library to generate the PB headers for others
to use.
> 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
