[
https://issues.apache.org/jira/browse/HBASE-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096016#comment-16096016
]
Phil Yang edited comment on HBASE-18334 at 7/21/17 9:27 AM:
------------------------------------------------------------
In [HBaseCon 2017 (in page 39)
|https://www.slideshare.net/HBaseCon/hbase-at-xiaomi?qid=96198dc1-bac8-4d13-a7df-64dbad476c34&v=&b=&from_search=18]
we showed some basic PE results.
was (Author: yangzhe1991):
In [HBaseCon 2017
|https://www.slideshare.net/HBaseCon/hbase-at-xiaomi?qid=96198dc1-bac8-4d13-a7df-64dbad476c34&v=&b=&from_search=18]
we showed some basic PE results.
> Remove sync client implementation and wrap async client under sync client
> interface
> -----------------------------------------------------------------------------------
>
> Key: HBASE-18334
> URL: https://issues.apache.org/jira/browse/HBASE-18334
> Project: HBase
> Issue Type: Task
> Reporter: Phil Yang
> Fix For: 3.0.0
>
>
> Since 2.0 we have async client, now we have two client implementations. We
> can implement an sync client (Table interface) by using async client, getting
> a CompletableFuture and then waiting it done directly. This can reduce the
> maintenance work at client side in the future.
> Async client is almost done, we tested the performance and it showed it has
> same performance with sync client. In branch-2 we can keep old sync client
> implementations and remove it in master branch (since 3.0).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
