apache
[CURATOR-379] unfixForNamespace corrupts child path when it contains namespace
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".
Originally reported by marvin.lillehaug, imported from: unfixForNamespace corrupts child path when it contains namespace
- status: Reopened
- priority: Minor
- resolution: Unresolved
- imported: 2025-01-21
GitHub user computerlove opened a pull request:
https://github.com/apache/curator/pull/194
CURATOR-379 unfixForNamespace corrupts child path when it contains namespace
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".
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/computerlove/curator CURATOR-379
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/194.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #194
commit 635b0e4005a0a03848ab59c9363c54d743ec2953
Author: Marvin Bredal Lillehaug
Date: 2017-01-11T10:00:01Z
commit 2b11a9614b501abd3344acaafc46231224c570fe
Author: Marvin Bredal Lillehaug
Date: 2017-01-11T10:04:49Z
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().