[
https://issues.apache.org/jira/browse/CURATOR-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105909#comment-15105909
]
ASF GitHub Bot commented on CURATOR-244:
----------------------------------------
Github user cammckenzie commented on the pull request:
https://github.com/apache/curator/pull/122#issuecomment-172672665
This looks ok to me.
> 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)
