phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramie Raufdeen (Jira)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-6523) Support for HBase Registry Implementations through Phoenix connection URL
Date Tue, 03 Aug 2021 19:59:00 GMT

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

Ramie Raufdeen updated PHOENIX-6523:
------------------------------------
    Description: 
https://issues.apache.org/jira/browse/HBASE-23305

https://issues.apache.org/jira/browse/HBASE-18095

 

HBase now supports a zookeeper-less connection strategy using a Master Registry implementation. 

 

For this to work, the client simply needs to set a list of <host:port>s of the HMaster
quorum

 
{code:java}
<property>
   <name>hbase.masters</name>
   <value>master1:16000,master2:16001,master3:16000</value>
</property>
{code}
 

To support opting into this from a Phoenix connection URL, we can introduce a "connector type"
as follows:
{code:java}
jdbc:phoenix+zk:hostname1,2,3...:<properties> 
jdbc:phoenix+hrpc:hostname1,2,3...:<properties>
jdbc:phoenix+bigtable:hostname1,2,3...:<properties>{code}

 Above are examples of opting into hrpc/zk/bigtable registry implementations of HBase.

 

If no connector is specified, the driver will default to a Zookeeper based connection.

 

  was:
https://issues.apache.org/jira/browse/HBASE-23305

https://issues.apache.org/jira/browse/HBASE-18095

 

HBase now supports a zookeeper-less connection strategy using a Master Registry implementation. 

 

For this to work, the client simply needs to set a list of <host:port>s of the HMaster
quorum

 
{code:java}
<property>
   <name>hbase.masters</name>
   <value>master1:16000,master2:16001,master3:16000</value>
</property>
{code}
 

To support opting into this from a Phoenix connection URL, we can introduce a "connector type"
as follows:
jdbc:phoenix+zk:hostname1,2,3...:<properties> 
jdbc:phoenix+hrpc:hostname1,2,3...:<properties>
jdbc:phoenix+bigtable:hostname1,2,3...:<properties>
Above are examples of opting into hrpc/zk/bigtable registry implementations of HBase.

 

If no connector is specified, the driver will default to a Zookeeper based connection.

 


> Support for HBase Registry Implementations through Phoenix connection URL
> -------------------------------------------------------------------------
>
>                 Key: PHOENIX-6523
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6523
>             Project: Phoenix
>          Issue Type: Improvement
>          Components: core
>            Reporter: Ramie Raufdeen
>            Priority: Major
>
> https://issues.apache.org/jira/browse/HBASE-23305
> https://issues.apache.org/jira/browse/HBASE-18095
>  
> HBase now supports a zookeeper-less connection strategy using a Master Registry implementation. 
>  
> For this to work, the client simply needs to set a list of <host:port>s of the
HMaster quorum
>  
> {code:java}
> <property>
>    <name>hbase.masters</name>
>    <value>master1:16000,master2:16001,master3:16000</value>
> </property>
> {code}
>  
> To support opting into this from a Phoenix connection URL, we can introduce a "connector
type" as follows:
> {code:java}
> jdbc:phoenix+zk:hostname1,2,3...:<properties> 
> jdbc:phoenix+hrpc:hostname1,2,3...:<properties>
> jdbc:phoenix+bigtable:hostname1,2,3...:<properties>{code}
>  Above are examples of opting into hrpc/zk/bigtable registry implementations of HBase.
>  
> If no connector is specified, the driver will default to a Zookeeper based connection.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message