Jakob Homan updated ZOOKEEPER-119:

    Attachment: ZOOKEEPER-119.patch

I went ahead and wrote up a patch to implement this functionality.  That way 
this behavior is inserted into the system as soon as possible and lessens the 
(already very small) chance that new code will be written that might conflict 
with it.

The patch:
   * Changes the create method to throw a BadArgumentsException when attempting 
to create a .zookeeper node, either in the root or nested
   * Inserts language into the create method javadoc explaining this znode name 
is reserved for future use by the server
   * Adds to the client unit tests to make sure .zookeeper nodes can't be 
created, but other, similar-sounding nodes, can be.

Hope this is helpful.

> Reserve ".zookeeper" node for server use.
> -----------------------------------------
>                 Key: ZOOKEEPER-119
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-119
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: server
>            Reporter: Patrick Hunt
>            Assignee: Benjamin Reed
>         Attachments: ZOOKEEPER-119.patch
> The server should not allow clients to create .zookeeper nodes in the node 
> hierarchy. These nodes should be reserved for zk future use, some ideas:
> * /.zookeeper/proc
> * /.zookeeper/stats
> * /.zookeeper/...
> * /.../.zookeeper/... (disallow both at root as well as child nodes)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to