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 #167: [CURATOR-352] SchemaViolation errors do not conta...
Date Mon, 03 Oct 2016 16:39:01 GMT
GitHub user Randgalt opened a pull request:

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

    [CURATOR-352] SchemaViolation errors do not contain enough information

    Better exceptions messaging when there is a Schema violation. This is much more useful
for debugging purposes

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

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

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

    https://github.com/apache/curator/pull/167.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 #167
    
----
commit 3735b50ba8ecdd60325bb9b1d65ff13ddc4836e4
Author: randgalt <randgalt@apache.org>
Date:   2016-10-03T16:34:53Z

    Better exceptions messaging when there is a Schema violation. This is much more useful
for debugging purposes

----


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