[
https://issues.apache.org/jira/browse/HADOOP-7557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204166#comment-13204166
]
Suresh Srinivas commented on HADOOP-7557:
-----------------------------------------
I initially liked the key, value idea that Doug proposed. However, after
thinking a bit, such a mechanism would require following functionality:
1. Ability to add optional keys that gets ignored on servers/clients where it
not understood.
2. Ability to add mandatory keys.
Doing this code where mandatory keys are enforced and optional keys are ignore
is not easy. Also capturing what key is optional and defining all this as an
interface definition (instead of free key, value text) is non trivial. These
are all the capabilities provided protobuf. Protobuf is already required part
of MRV2 and HDFS. Instead of building all that functionality, my vote is to use
protobuf.
> 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
