You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@zookeeper.apache.org by GitBox <gi...@apache.org> on 2022/06/29 03:07:33 UTC

[GitHub] [zookeeper] kezhuw commented on pull request #1820: ZOOKEEPER-4475: Fix NodeChildrenChanged delivered to recursive watcher

kezhuw commented on PR #1820:
URL: https://github.com/apache/zookeeper/pull/1820#issuecomment-1169484691

   @tisonkun Thank you for reviews. I have pushed fixup commit to resolve your comments. Regarding your concerns, I try to reply them here:
   1. The next sentence after the quoted one is "It can not be true.". From server's perspective, it is valid to attach standard child watches on descendants of node which is being watched in persistent recursive mode. So, basically, server is innocent to this. It has to be solved in client side. I explains this in code comments in fixup commit also.
   2. No. I observed this in writing tests for [zookeeper-client-rust](https://github.com/kezhuw/zookeeper-client-rust). In the first place, I observed quirk behaviors in situations where standard watches and persistent watches are attached on overlapping paths([ZOOKEEPER-4466](https://issues.apache.org/jira/browse/ZOOKEEPER-4466)). After discussion with @Randgalt in ZOOKEEPER-4466, I split out [ZOOKEEPER-4475](https://issues.apache.org/jira/browse/ZOOKEEPER-4475) as a bug report and ZOOKEEPER-4466 remains more like a feature request.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@zookeeper.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org