[jira] [Comment Edited] (ZOOKEEPER-3815) Support a new comprehensive parent znode watcher

["Jordan Zimmerman (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098121#comment-17098121 ] 

Jordan Zimmerman edited comment on ZOOKEEPER-3815 at 5/2/20, 10:39 PM:
-----------------------------------------------------------------------

How is this different from ZOOKEEPER-1416?


was (Author: randgalt):
How is this different than ZOOKEEPER-1416?

> Support a new comprehensive parent znode watcher
> ------------------------------------------------
>
>                 Key: ZOOKEEPER-3815
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3815
>             Project: ZooKeeper
>          Issue Type: New Feature
>            Reporter: Mohammad Arshad
>            Assignee: Mohammad Arshad
>            Priority: Major
>
> When a client registers this new watcher(for time being lets call it comprehensive parent znode watcher, we can give better name later.) on a parent znode then
> # Client should be notified on following events
>  ## When a child is added
>  ## When a child is deleted
>  ## When a child is updated
>  ## When parent is deleted
> # Client should be notified with znode data, This should be optional. There are many scenarios where znode data is always required. This can avoid unnecessary RPC calls.
>  # If Client keeps all child znode data in memory, there should be way to check whether client data is consistent with Zookeeper server data. This is to ensure that no notification is lost.
>  # This watcher should be persistent watcher, not one time watcher



--
This message was sent by Atlassian Jira
(v8.3.4#803005)