[
https://issues.apache.org/jira/browse/CURATOR-565?focusedWorklogId=790671&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-790671
]
ASF GitHub Bot logged work on CURATOR-565:
------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jul/22 02:48
Start Date: 14/Jul/22 02:48
Worklog Time Spent: 10m
Work Description: tisonkun commented on PR #354:
URL: https://github.com/apache/curator/pull/354#issuecomment-1183924193
@PhantomThief this patch may make sense as we use different logic handle
these flags between `CreateBuilder` and `ExistBuilder`. However, it may not be
resolved in this way but align to how `CreateBuilderImpl` handles
`createParentsIfNeeded` and `createParentsAsContainers`.
Issue Time Tracking
-------------------
Worklog Id: (was: 790671)
Time Spent: 1h 10m (was: 1h)
> checkExists didn't check useContainerParentsIfAvailable flag
> ------------------------------------------------------------
>
> Key: CURATOR-565
> URL: https://issues.apache.org/jira/browse/CURATOR-565
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.3.0
> Reporter: Tianzhou Wang
> Priority: Critical
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> When use zookeeper server 3.4.x with 3.5.x client.
> when use checkExists().creatingParentContainersIfNeeded() would lead
> Unimplemented Exception even dontUseContainerParents() was called for
> CuratorFrameworkFactory.builder().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
