[jira] [Resolved] (PHOENIX-7533) Fix broken compatibility for Zookeeper based ConnectionInfo

["Viraj Jasani (Jira)" <ji...@apache.org>]

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

Viraj Jasani resolved PHOENIX-7533.
-----------------------------------
    Resolution: Fixed

> Fix broken compatibility for Zookeeper based ConnectionInfo
> -----------------------------------------------------------
>
>                 Key: PHOENIX-7533
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7533
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.2.1
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>             Fix For: 5.3.0, 5.2.2
>
>
> Before PHOENIX-6523, ConnectionInfo used to provide hbase.zookeeper.quorum with Zookeeper host names separated by comma. With PHOENIX-6523, for zk registry, ConnectionInfo provides hbase.client.zookeeper.quorum with Zookeeper hosts and port values combined, separated by comma (e.g. "host1:1234,host2:2181,host3:9876" etc).
> For the purpose of creating HBase Connection, providing "hbase.client.zookeeper.quorum" is sufficient. However, Phoenix downstream applications that are using "hbase.zookeeper.quorum" value to determine which HTable threadpool to use for the given Connection can no longer function for cases like dual client where different HTable threadpools need to be used for different HBase connections.
> Given that Phoenix 5.1 client used to provide "hbase.zookeeper.quorum", 5.2 should not break this compatibility even though it provides "hbase.client.zookeeper.quorum" as additional Connection level configuration.



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