[
https://issues.apache.org/jira/browse/CURATOR-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kezhu Wang closed CURATOR-273.
------------------------------
Resolution: Won't Fix
It has been a decade since fa3ac29a35eb0c2db0f04541fe20a867f45070d3 or even
earlier. It is part of Curator API.
> Namespaces cannot start with /
> ------------------------------
>
> Key: CURATOR-273
> URL: https://issues.apache.org/jira/browse/CURATOR-273
> Project: Apache Curator
> Issue Type: Bug
> Components: Client
> Affects Versions: 2.9.0
> Reporter: Tom Dyas
> Priority: Minor
>
> Not so much of a bug as an API quirk: It is an error for namespaces to start
> with a / since Curator will always blindly append a / in front of the
> namespace. For example, see
> `curator-framework/src/main/java/org/apache/curator/framework/imps/NamespaceImpl.java`.
> Any reason why namespaces starting with a / are not supported? This requires
> application code to know whether the namespace starts with a / or not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
