Jordan Zimmerman commented on CURATOR-379:

I don't see how this issue can ever exhibit. The namespace is pre-pended going 
in and removed going out so it shouldn't matter. Do you have a test case that 
shows how this can happen? The current test case is a contrived call directly 

> unfixForNamespace corrupts child path when it contains namespace
> ----------------------------------------------------------------
>                 Key: CURATOR-379
>                 URL: https://issues.apache.org/jira/browse/CURATOR-379
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.11.1
>            Reporter: Marvin Bredal Lillehaug
>            Priority: Minor
> When a child path starts with the namespace unfixForNamespace removes the 
> namespace string, thus creating a invalid path.
> With namespace "foo" the result of unfixForNamespace("/foobar") is "bar".

This message was sent by Atlassian JIRA

Reply via email to