[
https://issues.apache.org/jira/browse/HBASE-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425896#comment-15425896
]
Anoop Sam John commented on HBASE-16432:
----------------------------------------
bq.Seems the current approach of implementing AsyncTable is in trouble as we
expose some netty classes in our public interfaces.
bq. Cut off the relationship between AsyncTable and Netty. We could implement
the AsyncTable with protobuf async stub.
Means we will be exposing PB async stuff instead of netty? That also should be
avoided. We should not be exposing any other third party class/interface
directly
> 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)
