[ 
https://issues.apache.org/jira/browse/CURATOR-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065613#comment-16065613
 ] 

ASF GitHub Bot commented on CURATOR-362:
----------------------------------------

Github user szekizoli commented on a diff in the pull request:

    https://github.com/apache/curator/pull/223#discussion_r124414693
  
    --- Diff: 
curator-framework/src/main/java/org/apache/curator/framework/imps/ExistsBuilderImpl.java
 ---
    @@ -185,7 +185,7 @@ public Stat forPath(String path) throws Exception
                 OperationAndData<String> operationAndData = new 
OperationAndData<String>(this, path, backgrounding.getCallback(), null, 
backgrounding.getContext(), watching);
                 if ( createParentContainersIfNeeded || createParentsIfNeeded )
                 {
    -                CreateBuilderImpl.backgroundCreateParentsThenNode(client, 
operationAndData, operationAndData.getData(), backgrounding, 
createParentContainersIfNeeded);
    +                CreateBuilderImpl.backgroundCreateParentsThenNode(client, 
operationAndData, operationAndData.getData(), backgrounding, 
client.getAclProvider(), createParentContainersIfNeeded);
    --- End diff --
    
    I think yes, it'd better if one can set the ACL as well with the option of 
creating parents, because the ability to set the ACL when creating a node is 
the expected behaviour.


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

Reply via email to