You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2016/09/08 12:38:20 UTC
[jira] [Resolved] (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 resolved HBASE-16432.
-------------------------------
Resolution: Fixed
Assignee: Duo Zhang
Fix Version/s: 2.0.0
Resolve as all sub-tasks have been resolved. Let's move on.
> 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
> Assignee: Duo Zhang
> Fix For: 2.0.0
>
>
> 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)