[
https://issues.apache.org/jira/browse/CURATOR-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707993#comment-17707993
]
Kezhu Wang commented on CURATOR-666:
------------------------------------
Another strip resides in {{makeCuratorEvent}}, before CURATOR-665 it resides in
{{sendBackgroundResponse}}. It has no relationship with CURATOR-665.
{code:java}
path = client.unfixForNamespace(path);
name = client.unfixForNamespace(name);
{code}
PS: There is no {{createResponseEvent}}. I turns out that I checked out dated
revision of CURATOR-665. Nothing changed.
> Background create strip namespace twice from path
> -------------------------------------------------
>
> Key: CURATOR-666
> URL: https://issues.apache.org/jira/browse/CURATOR-666
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 5.4.0
> Reporter: Kezhu Wang
> Assignee: Kezhu Wang
> Priority: Major
>
> {{CreateBuilderImpl::sendBackgroundResponse}} strips namespace twice:
> * One in body of {{sendBackgroundResponse}} or newly introduced
> {{createResponseEvent}}.
> * One in construction of {{CuratorEventImpl}}.
> This could cause incorrect resulting path if we are creating "/zoo" under
> "/zoo" namespace.
> This recall me ZOOKEEPER-4601, I verified that
> {{CuratorFramework::getConfig}} get "keeper/config" in "/zoo" and "/config"
> in "/zookeeper" namespace. We might need extra coordination with ZooKeeper
> community to maintain consistent between curator and zookeeper but I think we
> could fix `CreateBuilderImpl` independently. I remembered that I sent email
> in zookeeper dev list before, I will bump that up for discussion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
