[
https://issues.apache.org/jira/browse/CURATOR-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542809#comment-15542809
]
ASF GitHub Bot commented on CURATOR-352:
----------------------------------------
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 <[email protected]>
Date: 2016-10-03T16:34:53Z
Better exceptions messaging when there is a Schema violation. This is much
more useful for debugging purposes
----
> SchemaViolation errors do not contain enough information
> --------------------------------------------------------
>
> Key: CURATOR-352
> URL: https://issues.apache.org/jira/browse/CURATOR-352
> Project: Apache Curator
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 3.2.0
> Reporter: Jordan Zimmerman
> Assignee: Jordan Zimmerman
> Priority: Minor
> Fix For: 3.2.1
>
>
> When a SchemaViolation is thrown, it only has information about the schema
> entry. It would be much more useful if it also had information about the bad
> action - path, acl, etc. so that the problem can be debugged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
