curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CURATOR-362) Curator framework create API with ACL Mode is not adding the ACL to the parent nodes if select creatingParentsIfNeeded
Date Wed, 19 Jul 2017 14:42:00 GMT

     [ https://issues.apache.org/jira/browse/CURATOR-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jordan Zimmerman resolved CURATOR-362.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.4.0

> Curator framework create API with ACL Mode is not adding the ACL to the parent nodes
if select creatingParentsIfNeeded
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: CURATOR-362
>                 URL: https://issues.apache.org/jira/browse/CURATOR-362
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 2.9.1, 3.3.0
>            Reporter: Pavan
>             Fix For: 3.4.0
>
>
> 1) We are trying to create the node in the zookeeper using the curator framework 2.9.1
version by using the following api 
>  CuratorFramework.create().creatingParentsIfNeeded().withACL(authACList())
>                                 .forPath("/abc/xyz/", value)
> 2) Here ACL is applied only for xyz and the parent node like abc there is no ACL info.
So any client can add/remove data without ACL 
> Summary :  CuratorClient even though ACL is specified its not applying for the parents.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message