Hi guys, First, let me summarize changes of these two issues and associated prs here.
ZOOKEEPER-4475[1] reports that NodeChildrenChanged could be delivered to persistent recursive watchers if a child watch is created on descendants of node being watched using persistent recursive watch. pr#1820[2] solves this by filtering out NodeChildrenChanged events for persistent recursive watches on the client side. ZOOKEEPER-4466[3] reports that standard watch and persistent watch could not coexist on same path. pr#1859[4] introduces WatchStats to count and coexist different modes on same path. pr#1820 has been opened for a while but received no reviews. I think it is pretty simple and solves a simple bug. It should take a long time to review. For pr#1859, @eolivelli has given valuable comments. But both I and @eolivelli think ZOOKEEPER-4466 deserves more attention. So, basically, we need more reviewers to make sure pr#1859 goes in the right direction and breaks no sensible codes. It would be appreciated if any reviewers could take a look at these prs. Best, Kezhu Wang [1]: https://issues.apache.org/jira/browse/ZOOKEEPER-4475 [2]: https://github.com/apache/zookeeper/pull/1820 [3]: https://issues.apache.org/jira/browse/ZOOKEEPER-4466 [4]: https://github.com/apache/zookeeper/pull/1859
