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 6717017B6B for ; Tue, 19 May 2015 23:24:00 +0000 (UTC) Received: (qmail 30382 invoked by uid 500); 19 May 2015 23:24:00 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 30327 invoked by uid 500); 19 May 2015 23:24:00 -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 30314 invoked by uid 99); 19 May 2015 23:24:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2015 23:24:00 +0000 Date: Tue, 19 May 2015 23:24:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CURATOR-217) Use new Watcher Removal APIs in Curator Recipes 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-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551441#comment-14551441 ] ASF GitHub Bot commented on CURATOR-217: ---------------------------------------- GitHub user Randgalt opened a pull request: https://github.com/apache/curator/pull/82 [CURATOR-217] Use new Watcher Removal APIs in Curator Recipes You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/curator CURATOR-217 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/curator/pull/82.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 #82 ---- commit 58fcc548f87e3c787f82d48931e2e9992f6c3366 Author: randgalt Date: 2015-05-11T20:29:09Z first pass at implementation and a simple test commit d3672a5acbd2bdf0f8caa9b7c8ea07e9d4e4dd2a Author: randgalt Date: 2015-05-11T21:19:45Z wip commit 49b2fd3a8313cd05292e2ca8edb4b14b08f0de55 Author: randgalt Date: 2015-05-11T23:04:01Z more tests, refinements commit ff8eb4b2ec7c99258e62416453bef649fdc6220e Author: randgalt Date: 2015-05-12T01:48:16Z more tests commit 5030c198456150a82bf2a2a2e5aea75b65b2efc8 Author: randgalt Date: 2015-05-12T13:53:24Z wip ---- > Use new Watcher Removal APIs in Curator Recipes > ----------------------------------------------- > > Key: CURATOR-217 > URL: https://issues.apache.org/jira/browse/CURATOR-217 > Project: Apache Curator > Issue Type: Sub-task > Components: Recipes > Affects Versions: 3.0.0 > Reporter: Jordan Zimmerman > Assignee: Jordan Zimmerman > Fix For: 3.0.0 > > > Once the new Watcher Removal APIs are available, every Curator Recipe should be reviewed so that they clean up watchers as appropriate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)