Hi all,
Thank you for your information.
First, I agree that we should not introduce backward-incompatible changes
in patch releases.
Second, I have opened pr-1996[1] to fix the `getConfig` watcher path to
"/zookeeper/config".
Third, apologize for mistakes I made in the initial email.
A. It is
Il Ven 14 Apr 2023, 20:47 Chris Nauroth ha scritto:
> Thank you for the discussion, Kezhu.
>
> My take is that the behavior you proposed, with the received path always
> /zookeeper/config regardless of chroot, is the correct one. However, it's
> hard to know if anyone has coded workarounds on top
Thank you for the discussion, Kezhu.
My take is that the behavior you proposed, with the received path always
/zookeeper/config regardless of chroot, is the correct one. However, it's
hard to know if anyone has coded workarounds on top of the current
behavior, which would then break if we made the
Hi all,
Any thoughts on this?
Curator has similar issue reported as CURATOR-666[1]. I think it might be
worth to get Curator and ZooKeeper behave same in `getConfig`.
I replied this also to dev@curator for joint discussion. See my quotes and
ZOOKEEPER-4565[2], ZOOKEEPER-4601[3] for context.
[1]
Hi Devs,
Before ZOOKEEPER-4565[1], `ClientCnxn` uses following code to strip chroot:
```
// convert from a server path to a client path
if (chrootPath != null) {
String serverPath = event.getPath();
if (serverPath.compareTo(chrootPath) == 0) {
event.setPath("/");
} else if (se
