[
https://issues.apache.org/jira/browse/ZOOKEEPER-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622013#action_12622013
]
Patrick Hunt commented on ZOOKEEPER-119:
----------------------------------------
We wouldn't create a new API, a number of benefits in using the existing zk
read/write operations.
I don't think we should hide it - .zookeeper/stats for example could be used to
get useful information about the system/tree/node. I was thinking about
something along the lines of linux proc filesystem.
> 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
>
> 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.
