curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cammckenzie <...@git.apache.org>
Subject [GitHub] curator pull request: CURATOR-79 - Modified the 'withProtection' h...
Date Mon, 11 Aug 2014 01:27:37 GMT
GitHub user cammckenzie opened a pull request:

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

    CURATOR-79 - Modified the 'withProtection' handling, so that any failure

    that is not a ConnectionLossException or other KeeperException is
    treated the same as a ConnectionLossException. This means that if the
    thread gets interrupted, or encounters some sort of other error, during
    creation of a protected zNode, it will remove the affected zNode prior
    to rethrowing the exception.
    
    Exposed the debug UnhandledExceptionListener on the CuratorFrameworkImpl
    to reproduce this issue via a unit test.

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

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

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

    https://github.com/apache/curator/pull/35.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 #35
    
----
commit 5398b72f00ccc0f2ea995865fcaf92d73c6c5818
Author: Cam McKenzie <cammckenzie@apache.org>
Date:   2014-08-10T22:13:12Z

    CURATOR-79 - Modified the 'withProtection' handling, so that any failure
    that is not a ConnectionLossException or other KeeperException is
    treated the same as a ConnectionLossException. This means that if the
    thread gets interrupted, or encounters some sort of other error, during
    creation of a protected zNode, it will remove the affected zNode prior
    to rethrowing the exception.
    
    Exposed the debug UnhandledExceptionListener on the CuratorFrameworkImpl
    to reproduce this issue via a unit test.

----


---
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