[
https://issues.apache.org/jira/browse/CURATOR-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091773#comment-16091773
]
ASF GitHub Bot commented on CURATOR-362:
----------------------------------------
Github user szekizoli commented on the issue:
https://github.com/apache/curator/pull/223
I can prepare an update with the ability to add an ACL provider on the
ExistsBuilder if createParentNodesIfNeeded() is called, if you think that's
required for this change. It seems more consistent to me with having the option
to set the ACL.
> 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.4.14#64029)
