[
https://issues.apache.org/jira/browse/ZOOKEEPER-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michi Mutsuzaki resolved ZOOKEEPER-995.
---------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 3.5.0)
This is a dup of ZOOKEEPER-1027.
> C Client exposing chroot information
> ------------------------------------
>
> Key: ZOOKEEPER-995
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-995
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client
> Environment: $ uname -a
> Linux kaizen 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:48 UTC 2011
> i686 GNU/Linux
> $ java -version
> java version "1.6.0_22"
> Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
> Java HotSpot(TM) Server VM (build 17.1-b03, mixed mode)
> $ python -c "import zookeeper;print zookeeper.__version__"
> 3.4.0
> (latest zookeeper from the trunk)
> Reporter: Andrei Savu
> Attachments: ZOOKEEPER-995.patch
>
>
> When creating a new node while using a chrooted connection the client
> function returns the full path (no chroot prefix). I've encountered this
> while using zkpython and that's why I suppose it's a problem related to the C
> bindings. It seems like the java client it's not affected by the same issue
> (only tested using the command line interface). I will also attach a patch
> with failing test.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
