[
https://issues.apache.org/jira/browse/HBASE-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631229#comment-15631229
]
Duo Zhang commented on HBASE-16991:
-----------------------------------
I do not think this should go into the HBase codebase. You have lots of ways to
do the connection caching based on your usage and the SingletonAsyncConnection
is only one of them.
In our company, we store all the cluster configs on zk, and the users only need
to specify a cluster name when constructing a connection. So it is very easy
for us to implement a global connection cache as we can use the cluster name as
the key. And in other companies they may have other methods to cache
connections. I suggest you guys also introduce a thin layer on top of the hbase
client to do the connection caching work.
[~stack] What do you think?
Thanks.
> Make the initialization of AsyncConnection asynchronous
> -------------------------------------------------------
>
> Key: HBASE-16991
> URL: https://issues.apache.org/jira/browse/HBASE-16991
> Project: HBase
> Issue Type: Sub-task
> Components: Client
> Affects Versions: 2.0.0
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16991-v1.patch, HBASE-16991.patch
>
>
> Now the ConnectionFactory.createAsyncConnection is still blocking. We should
> make it return a CompletableFuture to make the async client fully
> asynchronous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
