[
https://issues.apache.org/jira/browse/ZOOKEEPER-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571505#comment-17571505
]
Enrico Olivelli commented on ZOOKEEPER-4601:
--------------------------------------------
I think that getConfig() should always receive the correct value from
/zookeeper/config
this is in contradiction with using chroot, in which you want a client to not
see the whole zookeeper database.
I think that the better behaviour is to let the client deal correctly with
/zookeeper/config, otherwise the behaviour won't be consistent
please start a thread on dev@
> 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
> Assignee: Kezhu Wang
> Priority: Blocker
>
> 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)
