You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2016/08/30 09:07:21 UTC

[jira] [Updated] (HBASE-16432) Revisit the asynchronous ipc implementation

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

Duo Zhang updated HBASE-16432:
------------------------------
    Component/s: rpc

> Revisit the asynchronous ipc implementation
> -------------------------------------------
>
>                 Key: HBASE-16432
>                 URL: https://issues.apache.org/jira/browse/HBASE-16432
>             Project: HBase
>          Issue Type: Umbrella
>          Components: rpc
>            Reporter: Duo Zhang
>
> Seems the current approach of implementing AsyncTable is in trouble as we expose some netty classes in our public interfaces.
> I agree that we should not do this. The AsyncTable should be implemented using the asynchronous protobuf stub, and we could use CompletableFuture or Deferred instead of netty's Future. I think the problem of netty's future is that it is tighten with netty's executor. This makes it impossible to use without netty.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)