[
https://issues.apache.org/jira/browse/CURATOR-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885025#comment-17885025
]
Kezhu Wang commented on CURATOR-715:
------------------------------------
Just in case for whoever comes from release note: The fix bumps up ZooKeeper to
3.9.2 which ZOOKEEPER-2590 is shipped.
> Check node existence bottom up in ZkPaths::mkdirs
> -------------------------------------------------
>
> Key: CURATOR-715
> URL: https://issues.apache.org/jira/browse/CURATOR-715
> Project: Apache Curator
> Issue Type: Bug
> Components: Client
> Reporter: Pablo Francisco Pérez Hidalgo
> Assignee: Pablo Francisco Pérez Hidalgo
> Priority: Major
> Fix For: 5.8.0
>
>
> After the changes in ZooKeeper derived from fixing issue
> https://issues.apache.org/jira/browse/ZOOKEEPER-2590 (All ZooKeeper versions
> from 3.8.4 and 3.9.2), it is not longer possible to check the existence of a
> node without READ access on its parent.
> When creating parents if needed, Apache Curator client checks the existence
> of all nodes in the path from the root node to the created one. However, this
> is not necessary, it is enough to check the existence of the nodes between
> the new node and the first existing ancestor.
> There are use cases where the first levels of a sub-tree are protected
> against read through ACLs. The current implementation makes it impossible to
> use `creatingParentsIfNeeded`.
>
> Patch: https://github.com/apache/curator/pull/506
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
