hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Sigoure (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)
Date Thu, 31 Oct 2013 16:01:27 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810371#comment-13810371
] 

Benoit Sigoure commented on HADOOP-9944:
----------------------------------------

!http://i.imgur.com/2ClmQri.gif!

Where to start... I don't even ...

Was there NO WAY you could have worked around this in your Java code?  Really?
Especially after having cut already 2 major releases with this code?

When will Hadoop finally grow up and provide guarantees both in terms of API compatibility
and wire-level compatibility?

If you got the API wrong, well, too bad.  Live with it.  Don't fucking break it.

(ノಠ益ಠ)ノ彡┻━┻

> 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
>             Fix For: 2.1.1-beta
>
>         Attachments: HADOOP-9944.patch, HADOOP-9944.patch, HADOOP-9944.patch
>
>
> RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID
is signed (-3).



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message