hadoop-zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ZOOKEEPER-237) Add a Chroot request
Date Wed, 24 Jun 2009 04:40:07 GMT

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

Hadoop QA commented on ZOOKEEPER-237:
-------------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12411450/ZOOKEEPER-237.patch
  against trunk revision 787789.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 23 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit
warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/129/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/129/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/129/console

This message is automatically generated.

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


Mime
View raw message