You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Kezhu Wang (Jira)" <ji...@apache.org> on 2022/02/22 02:42:00 UTC

[jira] [Assigned] (ZOOKEEPER-4472) Support persistent watchers removing individually

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kezhu Wang reassigned ZOOKEEPER-4472:
-------------------------------------

    Assignee: Kezhu Wang

> Support persistent watchers removing individually
> -------------------------------------------------
>
>                 Key: ZOOKEEPER-4472
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4472
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.6.3, 3.7.0
>            Reporter: Kezhu Wang
>            Assignee: Kezhu Wang
>            Priority: Major
>
> Persistent watchers could only be removed with {{WatcherType.Any}} now. I think it is meaningful to remove them individually as they are by naming persistent and will not auto removed in server side.
> Together with proposed solution from [ZOOKEEPER-4466], it will be clear that ZooKeeper has four kind of watchers:
> # Standard data watcher(which includes data and exist watcher in client side).
> # Standard child watcher.
> # Persistent node watcher(aka. data and child watcher for node).
> # Persistent recursive watcher(aka. data watcher for node and its descendants).
> See also [ZOOKEEPER-4471]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)