[
https://issues.apache.org/jira/browse/CURATOR-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018846#comment-16018846
]
ASF GitHub Bot commented on CURATOR-362:
----------------------------------------
Github user Randgalt commented on the issue:
https://github.com/apache/curator/pull/223
I'm not certain this is the correct behavior. The API contract implies only
that the ACL is set for the node being created. The ACL provider's job is to
manage any other nodes. This might be a breaking change for existing clients.
I'm -1 on this. I'm curious what other committers think.
> 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
> Reporter: Pavan
>
> 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.3.15#6346)
