[
https://issues.apache.org/jira/browse/HBASE-18334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Yang updated HBASE-18334:
------------------------------
Description:
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 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).
was:
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).
> 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 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)
