[
https://issues.apache.org/jira/browse/HBASE-23648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharath Vissapragada updated HBASE-23648:
-----------------------------------------
Description:
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.
Before Duo's Comment: don't see any obvious reason to not make it a singleton
(except for testing). This makes it more readable.
Edited to: Fix RawAsyncHBaseAdmin's creation of adhoc registry.
was:
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. -
> Re-use underlying connection registry in RawAsyncHBaseAdmin
> -----------------------------------------------------------
>
> Key: HBASE-23648
> URL: https://issues.apache.org/jira/browse/HBASE-23648
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 3.0.0
> Reporter: Bharath Vissapragada
> Assignee: Bharath Vissapragada
> Priority: Minor
>
> 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.
> Before Duo's Comment: don't see any obvious reason to not make it a singleton
> (except for testing). This makes it more readable.
> Edited to: Fix RawAsyncHBaseAdmin's creation of adhoc registry.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)