hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry He (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17221) Abstract out an interface for RpcServer.Call
Date Sat, 03 Dec 2016 21:01:58 GMT

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

Jerry He updated HBASE-17221:
    Attachment: HBASE-17221-v2.patch

v2 of the patch, more complete.

A new interface named 'RpcCall'.  Implementation class RpcServer.Call keeps the same name
for backward compatibility.  Let me know if you have a better name or approach.

The interface 'RpcCall' will be pass around in CallRunner, RpcServerInterface, etc.

This abstraction would also by used by coprocessor/Phoenix, instead of the implementation
class RpcServer.Call 

> Abstract out an interface for RpcServer.Call
> --------------------------------------------
>                 Key: HBASE-17221
>                 URL: https://issues.apache.org/jira/browse/HBASE-17221
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jerry He
>            Assignee: Jerry He
>             Fix For: 2.0.0
>         Attachments: HBASE-17221-v2.patch, HBASE-17221.patch
> RpcServer.Call is a concrete class, but it is marked as:
> {noformat}
> @InterfaceAudience.LimitedPrivate({HBaseInterfaceAudience.COPROC, HBaseInterfaceAudience.PHOENIX})
> {noformat}
> Let's abstract out an interface out of it for potential consumers that want to pass it

This message was sent by Atlassian JIRA

View raw message