You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Andrei Savu (JIRA)" <ji...@apache.org> on 2011/02/21 14:27:38 UTC

[jira] Updated: (ZOOKEEPER-995) C Client exposing chroot information

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrei Savu updated ZOOKEEPER-995:
----------------------------------

    Attachment: ZOOKEEPER-995.patch

This patch contains a failing test for zkpython.  

It creates a new node using a connection chrooted to "/zookeeper". As you can see bellow the returned path also contains the chroot prefix. 

{code}
     [exec] FAIL: test_sync_create_with_chroot (__main__.CreationTest)
     [exec] ----------------------------------------------------------------------
     [exec] Traceback (most recent call last):
     [exec]   File "src/test/create_test.py", line 64, in test_sync_create_with_chroot
     [exec]     self.assertEqual(ret, "/test")
     [exec] AssertionError: '/zookeeper/test' != '/test'

{code}

> 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira