You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2024/04/25 13:52:00 UTC

[jira] [Reopened] (HBASE-28436) Use connection url to specify the connection registry information

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

Duo Zhang reopened HBASE-28436:
-------------------------------

For applying addendum to address the naming issue, we changed ConnectionRegistryCreator to ConnectionRegistryURIFactory but forgot to change the name for sub classes...

> Use connection url to specify the connection registry information
> -----------------------------------------------------------------
>
>                 Key: HBASE-28436
>                 URL: https://issues.apache.org/jira/browse/HBASE-28436
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.0, 3.0.0-beta-2
>
>
> As describe in this email from [~ndimiduk]
> https://lists.apache.org/thread/98wqlkqvlnmpx3r7yrg9mw4pqz9ppofh
> The first advantage here is that, we can encode the connection registry implementation in the scheme of the connection url, so for replication, we can now support cluster key other than zookeeper, which is important for us to remove zookeeper dependency on our public facing APIs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)