[
https://issues.apache.org/jira/browse/HBASE-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631621#comment-15631621
]
Duo Zhang commented on HBASE-16991:
-----------------------------------
{quote}
How about for now adding this class to the connection factory class javadoc as
an example on how you might keep around your async connection
{quote}
I think the CAS trick is not easy to understand for end users... It is not easy
to find out the errors If they copy-paste it from the javadoc but missing some
important details... I think we could discuss it also in HBASE-17008? It is
also something like a connection cache.
{quote}
Do you want to make it more clear that Connection creation is expensive and
that app should therefore try and cache them in the javadoc somewhere around
here?
{quote}
Fine. Let me add this to the javadoc in ConnectionFactory.
> 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)
