[ 
https://issues.apache.org/jira/browse/PHOENIX-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17946346#comment-17946346
 ] 

Istvan Toth commented on PHOENIX-7495:
--------------------------------------

This has broken unit tests with HBase 2.4, [~lokiore].

{noformat}
[ERROR] Errors: 
[ERROR]   ClusterRoleRecordTest.testGetActiveUrl:142->getClusterRoleRecord:281 
» Runtime java.sql.SQLException: ERROR 102 (08001): Malformed connection url. 
Hbase version does not support Master registry for: 
jdbc:phoenix+rpc:zk1-1=2181,zk1-2=2181
[ERROR]   ClusterRoleRecordTest.testGetRole:248->getClusterRoleRecord:281 » 
Runtime java.sql.SQLException: ERROR 102 (08001): Malformed connection url. 
Hbase version does not support Master registry for: 
jdbc:phoenix+rpc:zk1-1=2181,zk1-2=2181
[ERROR]   
ClusterRoleRecordTest.testHasSameInfoDifferentHostOrder:214->getClusterRoleRecord:281
 » Runtime java.sql.SQLException: ERROR 102 (08001): Malformed connection url. 
Hbase version does not support Master registry for: 
jdbc:phoenix+rpc:zk2-1=2181,zk2-2=2181
[ERROR]   
ClusterRoleRecordTest.testHasSameInfoDifferentZKOrder:198->getClusterRoleRecord:281
 » Runtime java.sql.SQLException: ERROR 102 (08001): Malformed connection url. 
Hbase version does not support Master registry for: 
jdbc:phoenix+rpc:zk2-1=2181,zk2-2=2181
[ERROR]   
ClusterRoleRecordTest.testHasSameInfoNegative:228->getClusterRoleRecord:281 » 
Runtime java.sql.SQLException: ERROR 102 (08001): Malformed connection url. 
Hbase version does not support Master registry for: 
jdbc:phoenix+rpc:zk1-1=2181,zk1-2=2181
[ERROR]   ClusterRoleRecordTest.testHasSameInfo:184->getClusterRoleRecord:281 » 
Runtime java.sql.SQLException: ERROR 102 (08001): Malformed connection url. 
Hbase version does not support Master registry for: 
jdbc:phoenix+rpc:zk1-1=2181,zk1-2=2181
[ERROR]   ClusterRoleRecordTest.testIsNewerThan:158->getClusterRoleRecord:281 » 
Runtime java.sql.SQLException: ERROR 102 (08001): Malformed connection url. 
Hbase version does not support Master registry for: 
jdbc:phoenix+rpc:zk1-1=2181,zk1-2=2181
[ERROR]   
ClusterRoleRecordTest.testReadWriteJsonToFile:90->getClusterRoleRecord:281 » 
Runtime java.sql.SQLException: ERROR 102 (08001): Malformed connection url. 
Hbase version does not support Master registry for: 
jdbc:phoenix+rpc:zk1-1=2181,zk1-2=2181
[ERROR]   ClusterRoleRecordTest.testToAndFromJson:131->getClusterRoleRecord:281 
» Runtime java.sql.SQLException: ERROR 102 (08001): Malformed connection url. 
Hbase version does not support Master registry for: 
jdbc:phoenix+rpc:zk1-1=2181,zk1-2=2181
[ERROR]   
ClusterRoleRecordTest.testToPrettyString:260->getClusterRoleRecord:281 » 
Runtime java.sql.SQLException: ERROR 102 (08001): Malformed connection url. 
Hbase version does not support Master registry for: 
jdbc:phoenix+rpc:zk1-1=2181,zk1-2=2181

{noformat}


> Support for HBase Registry Implementations in Pheonix HA Connections
> --------------------------------------------------------------------
>
>                 Key: PHOENIX-7495
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7495
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Lokesh Khurana
>            Assignee: Lokesh Khurana
>            Priority: Major
>             Fix For: 5.3
>
>
> PHOENIX-6523 adds support for MasterRegistry and RPCConnectionRegistry to 
> Phoenix but only for Normal Phoenix Connections. This Jira is an extension of 
> that to provide different registry supports in Phoenix HA Connections.
> For this Jira Initial bootstrap ha phoenix url to connect to clusters will be 
> same containing ZK urls to get Cluster Role Records
> For this to work we are introducing new parameter in Cluster Role Record :- 
> Registry Type (which can be ZK/Master/RPC...) and url param of CRR will 
> contain the hostnames with respect to registry type. 
> For Backward Compatibility if RegistryType is not there then we will assume 
> it's ZK 



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

Reply via email to