[ 
https://issues.apache.org/jira/browse/CURATOR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268880#comment-15268880
 ] 

ASF GitHub Bot commented on CURATOR-322:
----------------------------------------

GitHub user Randgalt opened a pull request:

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

    [CURATOR-322] Schema/documentation support

    See Issue for details.

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

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

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

    https://github.com/apache/curator/pull/147.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 #147
    
----
commit ef1658c17e3f991968932c0bef94d547ecea790d
Author: randgalt <[email protected]>
Date:   2016-05-02T19:06:15Z

    initial work on schema validation

commit da760f96cc5e553e7475505f282bce60a5da3056
Author: randgalt <[email protected]>
Date:   2016-05-02T19:16:48Z

    forgot sequential

commit f25a81263a5cfb4895f4aa147eec8374dbbb510e
Author: randgalt <[email protected]>
Date:   2016-05-02T21:07:26Z

    Further implementation of schema support

commit df3c1c4b059fc9c930716f91230dbe8a466fef08
Author: randgalt <[email protected]>
Date:   2016-05-02T21:12:47Z

    Log the schema at start

commit 7f27631cb8d11e7026deca5e6848d9a1e584f0d3
Author: randgalt <[email protected]>
Date:   2016-05-02T21:16:52Z

    needs new arg

commit 33534a099884fc8336c85aaf518e10485de4efe1
Author: randgalt <[email protected]>
Date:   2016-05-02T21:35:55Z

    documentation and cleanup

commit 3f47f6a384d5a7459ec088b3c621a48c04731ebc
Author: randgalt <[email protected]>
Date:   2016-05-02T22:03:49Z

    Make regex optional and add a key to each schema

commit f83c8efcfbd4781d64ef4e7ef37c12ff68de12a1
Author: randgalt <[email protected]>
Date:   2016-05-02T22:03:54Z

    Make regex optional and add a key to each schema

commit 8ccfdebddfd9ce3d23d35f9ae94d5be77fa538a8
Author: randgalt <[email protected]>
Date:   2016-05-02T22:09:40Z

    more doc

commit 734f4533808f1a4b8b8086407476bca8862339ff
Author: randgalt <[email protected]>
Date:   2016-05-03T02:41:25Z

    more doc, some testing, schema set loader

commit 4e667686332fe43114b7e093569a988a1a85c819
Author: randgalt <[email protected]>
Date:   2016-05-03T04:36:48Z

    more tests, fixes

commit e3ec920454206493317ec9cc49aaa21be48ee0ad
Author: randgalt <[email protected]>
Date:   2016-05-03T04:40:33Z

    licenses

commit 30d83b87e9ddcee78d21615d45995f13ef1832ff
Author: randgalt <[email protected]>
Date:   2016-05-03T04:41:26Z

    moved test to better package

commit 450976f3d5c629b83d556b4f840ac844bb620830
Author: randgalt <[email protected]>
Date:   2016-05-03T04:51:51Z

    Include path in data validator - tests for data validator

commit 923a2d8b93d348bcacc6541be5f4013423ce43d2
Author: randgalt <[email protected]>
Date:   2016-05-03T14:40:55Z

    removed SchemaKey - it was overkill

commit ae6cb4be4ee56215bef26e8d7fb5139d9b81d026
Author: randgalt <[email protected]>
Date:   2016-05-03T15:19:46Z

    test transactions

----


> 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 message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to