hadoop-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-589) When create a znode, a NULL ACL parameter cannot be accepted
Date Mon, 01 Feb 2010 19:40:18 GMT

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

Benjamin Reed commented on ZOOKEEPER-589:

i think we should fix the client docs to reflect this behavior. "ACL of the parent" is a bit
ambiguous if the parent's ACL changes after the create. it also will be problematic when we
do federated ZooKeeper.

> When create a znode, a NULL ACL parameter cannot be accepted
> ------------------------------------------------------------
>                 Key: ZOOKEEPER-589
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-589
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.2.1
>         Environment: Linux db-passport-test05.vm 2.6.9_5-4-0-5 #1 SMP Tue Apr 14 15:56:24
CST 2009 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Qian Ye
>             Fix For: 3.3.0
> In the comments of client C API which associated with creating znode, eg. zoo_acreate,
it is said that the initial ACL of the node "if null, the ACL of the parent will be used".
However, the it doesn't work. When execute this kind of request at the server side, it raises
InvalidACLException. The source code show that, the function fixupACL return false when it
get a null ACL. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message