hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6422) permit RPC protocols to be implemented by Avro
Date Thu, 10 Dec 2009 20:08:18 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Doug Cutting updated HADOOP-6422:

    Attachment: HADOOP-6422.patch

Here's a patch that makes the RPC backend pluggable protocol-by-protocol.  The public API
of RPC.java is unchanged, but it now delegates to an RpcEngine implementation.  The existing
implementation is moved to WritableRpcEngine.  AvroRpc is modified to implement RpcEngine.
 No new public APIs are introduced.

AvroRpc is no longer public, which may be an incompatible change.  It was introduced in 0.21,
which has not yet been released, so we could either:
 - backport this change to 0.21
 - declare that AvroRpc was experimental, little used, and permit this incompatible change
from 0.21 to 0.22.
 - keep AvroRpc public in 0.22, with its prior static methods, for compatibility with 0.21.

I prefer one of the first two options, since I think, going forward, we want to encourage
the use of a single RPC API, and not have to maintain multiple APIs long-term.

I have run HDFS and MapReduce tests against this, and they pass.

> permit RPC protocols to be implemented by Avro
> ----------------------------------------------
>                 Key: HADOOP-6422
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6422
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: ipc
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 0.22.0
>         Attachments: HADOOP-6422.patch
> To more easily permit Hadoop to evolve to use Avro RPC, I propose to change RPC to use
different implementations for clients and servers based on the configuration.  This is not
intended as an end-user configuration: only a single RPC implementation will be supported
in a given release, but rather a tool to permit us to more easily develop and test new RPC
implementations.  As such, the configuration parameters used would not be documented.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message