Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3373918FA6 for ; Mon, 18 Jan 2016 22:54:40 +0000 (UTC) Received: (qmail 69276 invoked by uid 500); 18 Jan 2016 22:54:40 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 69226 invoked by uid 500); 18 Jan 2016 22:54:40 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 69206 invoked by uid 99); 18 Jan 2016 22:54:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2016 22:54:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E175E2C1F57 for ; Mon, 18 Jan 2016 22:54:39 +0000 (UTC) Date: Mon, 18 Jan 2016 22:54:39 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CURATOR-290) Watcher removal is not removing internal Curator data structures MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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 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)