curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randgalt <...@git.apache.org>
Subject [GitHub] curator pull request: [CURATOR-332] Internal watcher tracking for ...
Date Thu, 26 May 2016 22:01:39 GMT
GitHub user Randgalt opened a pull request:

    https://github.com/apache/curator/pull/154

    [CURATOR-332] Internal watcher tracking for new WatcherRemoveCuratorFramework feature
is not correct

    Reworked WatcherRemovalManager. It now stores watchers only on successful operations.
This is more like how ZK does it.
    
    Also, exists watcher must be stored when there is a NoNode result.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/curator CURATOR-332

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/154.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 #154
    
----
commit f59f23c703815317d4ef1d39e2b815e402d1559b
Author: randgalt <randgalt@apache.org>
Date:   2016-05-26T21:59:08Z

    Reworked WatcherRemovalManager. It now stores watchers only on successful operations.
This is more like how ZK does it.
    Also, exists watcher must be stored when there is a NoNode result.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message