[
https://issues.apache.org/jira/browse/ZOOKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Reed updated ZOOKEEPER-237:
------------------------------------
Status: Open (was: Patch Available)
looks good. two comments:
* feel free to ignore this one: when you setup hostname and chroot, i think the
code is simpler if you hostname = strdup(host) and then poke a null into
hostname to strip off the chroot
* we need to make sure we have total coverage for the testcases. you are
missing a couple of the synchronous calls and you need to add the asynchronous
calls. (i know it is tedious)
> 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
> Reporter: Benjamin Reed
> Assignee: Mahadev konar
> Priority: Minor
> Fix For: 3.2.0
>
> Attachments: ZOOKEEPER-237.patch, ZOOKEEPER-237.patch,
> ZOOKEEPER-237.patch
>
>
> 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.
