[jira] [Commented] (CURATOR-362) Curator framework create API with ACL Mode is not adding the ACL to the parent nodes if select creatingParentsIfNeeded

[ASF GitHub Bot (JIRA)]

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

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

Github user Randgalt commented on the issue:

    https://github.com/apache/curator/pull/223
  
    We can add a new method to `ACLable`:
    
    ```
    public interface ACLable<T>
    {
        public T withACL(List<ACL> aclList);
    
        public T withACL(List<ACL> aclList, boolean applyToParents);
    }
    ```


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