You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Bharath Vissapragada (Jira)" <ji...@apache.org> on 2020/01/06 23:00:00 UTC

[jira] [Updated] (HBASE-23648) Re-use underlying connection registry in RawAsyncHBaseAdmin

     [ https://issues.apache.org/jira/browse/HBASE-23648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bharath Vissapragada updated HBASE-23648:
-----------------------------------------
    Summary: Re-use underlying connection registry in RawAsyncHBaseAdmin  (was: Evaluate making ConnectionRegistry a singleton class)

> Re-use underlying connection registry in RawAsyncHBaseAdmin
> -----------------------------------------------------------
>
>                 Key: HBASE-23648
>                 URL: https://issues.apache.org/jira/browse/HBASE-23648
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>    Affects Versions: 3.0.0
>            Reporter: Bharath Vissapragada
>            Assignee: Bharath Vissapragada
>            Priority: Major
>
> Based on the discussion between [~stack] and I in the code review for HBASE-23305, the current usage of ConnectionRegistry is ad-hoc, sometimes multiple times per connection.
> I don't see any obvious reason to not make it a singleton (except for testing). This makes it more readable. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)