[ https://issues.apache.org/jira/browse/HBASE-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425904#comment-15425904 ]
Duo Zhang edited comment on HBASE-16432 at 8/18/16 5:12 AM: ------------------------------------------------------------ {quote} Means we will be exposing PB async stuff instead of netty? {quote} Not necessary. The AsyncTable interface will use CompletableFuture or something like Deferred. The PB stuffs are only used in the implementation. was (Author: apache9): {quota} Means we will be exposing PB async stuff instead of netty? {quota} Not necessary. The AsyncTable interface will use CompletableFuture or something like Deferred. The PB stuffs are only used in the implementation. > Revisit the asynchronous ipc implementation > ------------------------------------------- > > Key: HBASE-16432 > URL: https://issues.apache.org/jira/browse/HBASE-16432 > Project: HBase > Issue Type: Umbrella > 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)