[
https://issues.apache.org/jira/browse/CURATOR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268905#comment-15268905
]
ASF GitHub Bot commented on CURATOR-322:
----------------------------------------
Github user alexbrasetvik commented on a diff in the pull request:
https://github.com/apache/curator/pull/147#discussion_r61902387
--- Diff: curator-framework/src/test/resources/schema1.json ---
@@ -0,0 +1,9 @@
+[
+ {
+ "name": "test",
--- End diff --
The tests would read a bit easier if the name hinted to the contents of the
schema, like `ephemeralNotSequential`?
> Schema support - path validation and documentation
> --------------------------------------------------
>
> Key: CURATOR-322
> URL: https://issues.apache.org/jira/browse/CURATOR-322
> Project: Apache Curator
> Issue Type: New Feature
> Components: Framework
> Affects Versions: 3.1.0
> Reporter: Jordan Zimmerman
> Assignee: Jordan Zimmerman
> Fix For: TBD
>
>
> ZooKeeper applications are heavily dependent on correct usage of paths,
> watchers, ZNode data, etc. Currently, there is no mechanism for validating
> and documenting this. It would be nice to have some kind of schema system
> that allows for this.
> This issue provides several items of functionality: a) ZNode path
> documentation; b) ZNode path validation; c) keyed reference to ZNode paths.
> Both items are defined in a new class, Schema. A Curator Schema specifies a
> ZNode path (or regex pattern), documentation for that path, and the
> operations that are allowed on that path. Additionally, a set of Schema
> objects are collected into a SchemaSet object that allows any Schema (and
> thereby its path) to be retrieved via a symbolic name. This should make path
> management in ZK applications easier. Lastly, a utility is provided to load
> SchemaSets from a file/stream in JSON format.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
