zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Reed (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ZOOKEEPER-237) Add a Chroot request
Date Tue, 05 May 2009 16:38:30 GMT

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

Benjamin Reed commented on ZOOKEEPER-237:

could the chroot be done entirely in the client library? it's basically just prepending a
prefix to all the requests and stripping the prefix off on watches.

> Add a Chroot request
> --------------------
>                 Key: ZOOKEEPER-237
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-237
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: c client, java client, server
>            Reporter: Benjamin Reed
>            Priority: Minor
>             Fix For: 3.2.0
> 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.

View raw message