[
https://issues.apache.org/jira/browse/CURATOR-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105922#comment-15105922
]
ASF GitHub Bot commented on CURATOR-290:
----------------------------------------
GitHub user Randgalt opened a pull request:
https://github.com/apache/curator/pull/126
[CURATOR-290] Make sure NamespaceWatcherMap is cleared
Make sure NamespaceWatcherMap is cleared when the corresponding watcher is
removed via new APIs. Added tests to ensure this.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/curator CURATOR-290
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/126.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #126
----
commit adb4be47ca6e64962aae3067412cc76aa4b0cd22
Author: randgalt <[email protected]>
Date: 2016-01-18T22:53:27Z
Make sure NamespaceWatcherMap is cleared when the corresponding watcher is
removed via new APIs. Added tests to ensure this.
----
> Watcher removal is not removing internal Curator data structures
> ----------------------------------------------------------------
>
> Key: CURATOR-290
> URL: https://issues.apache.org/jira/browse/CURATOR-290
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 3.0.0
> Reporter: Jordan Zimmerman
> Assignee: Jordan Zimmerman
> Fix For: 3.0.1
>
>
> In the new RemoveWatchesBuilder APIs, the watchers should also be removed
> from Curator's NamespaceWatcherMap.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
