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

Istvan Toth updated HBASE-29248:
--------------------------------
    Release Note: 
Originally, hbase properties with the "hbase.zookeeper.property." prefix were 
set as System properties, later ZKClientConfig properties by replacing the 
"hbase.zookeeper.property." prefix with a "zookeeper." prefix.

This was accidentally changed in Hbase 2.5.9 and 2.6.0, so that 
"hbase.zookeeper.property." was simply removed, which broke configurations that 
relied on the original behaviour.

HBase 2.5.12 and 2.6.3 reverts the accidental change, and restores the original 
behaviour of replacing the "hbase.zookeeper.property." prefix with a 
"zookeeper." prefix for the ZK client config properties.


> HBASE-28529 made an incompatible change to hbase.zookeeper.property handling
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-29248
>                 URL: https://issues.apache.org/jira/browse/HBASE-29248
>             Project: HBase
>          Issue Type: Bug
>          Components: Zookeeper
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>              Labels: pull-request-available
>
> Before HBASE-28529 , HBase took the properties with the 
> _hbase.zookeeper.property._ , removed the _hbase.zookeeper.property._ and 
> added the _zookeeper._ prefix, then set this as a system property.
> When HBASE-28529 has rewritten this to use ZKClientConfig, it forgot to add 
> the _zookeeper._  prefix to the property. ZK uses the exact same names for 
> the ZKClientConfig properties and System properties (where both are supported)
> For example,  to set the _zookeeper.client.secure_ property, earlier we had 
> to set {_}hbase.zookeeper.property.{_}{_}client.secure ,{_} while now we need 
> to set {_}hbase.zookeeper.property.zookeeper.{_}{_}client.secure{_}
> This is an incompatible change, which is likely to cause problems for users 
> that rely on this feature.



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

Reply via email to