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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
