[
https://issues.apache.org/jira/browse/ZOOKEEPER-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zili Chen resolved ZOOKEEPER-4601.
----------------------------------
Resolution: Duplicate
Resolved alongside ZOOKEEPER-838.
> Define getConfig Watcher behavior in chroot ZooKeeper
> -----------------------------------------------------
>
> Key: ZOOKEEPER-4601
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4601
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Reporter: Kezhu Wang
> Assignee: Kezhu Wang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> After ZOOKEEPER-4565, {{getConfig}} watcher will receive path for zookeeper
> config node "/zookeeper/config". But if the path {{getConfig}} watcher
> received is somewhat sensitive to chroot path.
> * With chroot path "/zookeeper", {{getConfig}} will receive path "/config".
> * With other chroot paths, {{getConfig}} will receive path
> "/zookeeper/config".
> I think we should define what path {{getConfig}} will get formally to avoid
> unnoticed behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
