[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650337#action_12650337
 ] 

Patrick Hunt commented on ZOOKEEPER-237:
----------------------------------------

I like the idea of being able to bind an application to a particular subtree. 
However this binding should be opaque to the client - the client should not be 
specifying (or circumventing) the root. The operator should map a credential to 
a root (ala aws s3)

> Add a Chroot request
> --------------------
>
>                 Key: ZOOKEEPER-237
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-237
>             Project: Zookeeper
>          Issue Type: New Feature
>            Reporter: Benjamin Reed
>            Priority: Minor
>
> It would be nice to be able to root ZooKeeper handles at specific points in 
> the namespace, so that applications that use ZooKeeper can work in their own 
> rooted subtree.
> For example, if ops decides that application X can use the subtree /apps/X 
> and application Y can use the subtree /apps/Y, X can to a chroot to /apps/X 
> and then all its path references can be rooted at /apps/X. Thus when X 
> creates the path "/myid", it will actually be creating the path 
> "/apps/X/myid".
> There are two ways we can expose this mechanism: 1) We can simply add a 
> chroot(String path) API, or 2) we can integrate into a service identifier 
> scheme for example zk://server1:2181,server2:2181/my/root. I like the second 
> form personally.

-- 
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