[
https://issues.apache.org/jira/browse/HBASE-28436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847337#comment-17847337
]
Nick Dimiduk commented on HBASE-28436:
--------------------------------------
[~frostruan] This was discussed at some length in the PR. For now, there are
only "explicit" implementations, without fallback to defaults. Using this
feature must be explicit and fully specified. I hope that this will relax in
the future, and if you've like to see more flexibility, please share your
thoughts in those design discussions. Thanks.
> 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)
