You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Kezhu Wang (Jira)" <ji...@apache.org> on 2022/07/26 13:44:00 UTC

[jira] [Created] (ZOOKEEPER-4601) Define getConfig Watcher behavior in chroot ZooKeeper

Kezhu Wang created ZOOKEEPER-4601:
-------------------------------------

             Summary: Define getConfig Watcher behavior in chroot ZooKeeper
                 Key: ZOOKEEPER-4601
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4601
             Project: ZooKeeper
          Issue Type: Improvement
          Components: java client
            Reporter: Kezhu Wang


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)