curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randgalt <>
Subject [GitHub] curator pull request #178: [CURATOR-365] backgroundCreateParentsThenNode() i...
Date Mon, 19 Dec 2016 15:43:13 GMT
GitHub user Randgalt opened a pull request:

    [CURATOR-365] backgroundCreateParentsThenNode() ignores exceptions too crudely


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

    $ git pull CURATOR-365

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #178
commit 10e2d9db821ed03903f00ce4f23e431168fce910
Author: randgalt <>
Date:   2016-11-11T13:33:36Z

    [maven-release-plugin] prepare release apache-curator-2.11.1

commit 96a0a944e25f6b49c90e247a5095bae596c6cbc3
Author: randgalt <>
Date:   2016-11-11T13:33:47Z

    [maven-release-plugin] prepare for next development iteration

commit 8abb54b2e9790f3afba76a85aa2c407c05c3052e
Author: randgalt <>
Date:   2016-11-11T13:39:56Z

    back to 2.11.1-SNAPSHOT

commit f8c6a0933737bc3044eeddc1a90aafda20febca5
Author: randgalt <>
Date:   2016-11-11T13:42:04Z

    [maven-release-plugin] prepare release apache-curator-2.11.1

commit fbb98a1ed6b43378627d89b8f6b74c49c5deef25
Author: randgalt <>
Date:   2016-11-11T13:42:15Z

    [maven-release-plugin] prepare for next development iteration

commit 0a3e8490b64ad8466989726ac6215b357fed3152
Author: randgalt <>
Date:   2016-12-19T14:52:19Z

    Merge branch 'master' of

commit 125dc969942a89f498b06e190cb38f9819c7bb37
Author: randgalt <>
Date:   2016-12-19T15:41:11Z

    if an async create() with creatingParentContainersIfNeeded() was called with a connection
that wasn't properly authorized to create the parent nodes. backgroundCreateParentsThenNode()
was treating all KeeperExceptions as ignorable (i.e. retry-able) which would cause an infinite


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 or file a JIRA ticket
with INFRA.

View raw message