[
https://issues.apache.org/jira/browse/HBASE-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631456#comment-15631456
]
Yu Li commented on HBASE-16991:
-------------------------------
On the contrary, I think we should make it easy for user to use, HBase is a
database not library. Especially when previous released versions (and even
latest stable version) supports connection caching, I call this a *behavior
change* which causes inconvenience for users.
I understand you have some service layer on top of HBase there, but it just
proves HBase is not convenient enough to use so you wrapped it up. Honestly I
think this is disadvantage of HBase rather than advantage.
OTOH, if we depend on the way user uses HBase to make sure of some correctness
(like only create a connection per process to avoid too many connections setup
to Zookeeper/RS), I think we are not doing good.
Maybe this is not the right place to discuss this connection caching topic, but
we already brought it up so just let it be (Smile). [~Apache9] [~stack]
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)
