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

["Zili Chen (Jira)" <ji...@apache.org>]

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

Zili Chen resolved ZOOKEEPER-4472.
----------------------------------
    Resolution: Fixed

Master via e8b2fbeb101e22378aa47df291cc9ca6e58e1e8d.

> 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: Blocker
>              Labels: pull-request-available
>             Fix For: 3.9.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> 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.10#820010)