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

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

GitHub user Randgalt opened a pull request:

    https://github.com/apache/curator/pull/122

    [CURATOR-244] ZKPaths.mkdirs() was always passing the full path to the 
aclProvider instead of the subpath being created

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/curator CURATOR-244

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/122.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #122
    
----
commit d6da90e8e746c92cc182e62a96fc2a9182fd1a15
Author: randgalt <[email protected]>
Date:   2016-01-12T15:13:12Z

    ZKPaths.mkdirs() was always passing the full path to the aclProvider 
instead of the subpath being created

----


> Creating parents with ACLProvider puts wrong ACLs on znodes
> -----------------------------------------------------------
>
>                 Key: CURATOR-244
>                 URL: https://issues.apache.org/jira/browse/CURATOR-244
>             Project: Apache Curator
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: John Vines
>            Assignee: Jordan Zimmerman
>             Fix For: 2.9.2
>
>
> Currently, if I create /foo/bar/baz and /foo doesn't exist it will create the 
> whole hierarchy, but it will create /foo and /foo/bar with the ACLs the 
> provider provides for /foo/bar/baz. I would expect it to consult the 
> ACLProvider for the right znode (which seems totally doable but for some 
> reason it passes in the wrong path to the provider when creating parents) or 
> not ACL the parent znode.
> This is similar to CURATOR-221, but I think this behavior makes for a pretty 
> bad user experience as it's not simply a case of checking how you namespace a 
> curatorframework.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to