[
https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768475#comment-13768475
]
Binglin Chang commented on HADOOP-9944:
---------------------------------------
Hi Arun,
Currently change uint32 to int32 still keeps wire compatibility, cause uint32
and int32 uses the same encoding. But change field id will break compatibility.
If we do permit breaking compatibility, sint32 is better cause it uses ZigZag
encoding which uses much less spaces for small negative intergers.
See https://developers.google.com/protocol-buffers/docs/encoding
> RpcRequestHeaderProto defines callId as uint32 while
> ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-9944
> URL: https://issues.apache.org/jira/browse/HADOOP-9944
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Priority: Blocker
> Attachments: HADOOP-9944.patch, HADOOP-9944.patch
>
>
> RpcRequestHeaderProto defines callId as uint32 while
> ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
