hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Radia (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7557) Make IPC header be extensible
Date Mon, 13 Feb 2012 17:45:06 GMT

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

Sanjay Radia commented on HADOOP-7557:
--------------------------------------

>Sanjay> ... can help us provide 20 compatibility
>I'm confused. If you switch the RPC headers to protobuf how can you provide 20 compatibility?
Not PB but the RPC engine can allow older impls to live side by side. 

>The reason we removed Avro was that implementing RpcEngine alone was no longer sufficient:
there were assumptions that Protobuf was used in other places in the code. RpcEngine is currently
a broken abstraction, providing a false claim of plugability.

Doug your model was that setting a single flag would allow one to switch from one serialization
to another.
The model that was implemented allowed one use one or another engine but one had to have code
to do that.

                
> 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

        

Mime
View raw message