Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B89F1106D9 for ; Sat, 28 Dec 2013 16:30:04 +0000 (UTC) Received: (qmail 10462 invoked by uid 500); 28 Dec 2013 16:29:59 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 10380 invoked by uid 500); 28 Dec 2013 16:29:52 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 10368 invoked by uid 99); 28 Dec 2013 16:29:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Dec 2013 16:29:49 +0000 X-ASF-Spam-Status: No, hits=4.0 required=5.0 tests=HTML_MESSAGE,HTML_OBFUSCATE_10_20,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of scoulibaly@gmail.com designates 74.125.82.54 as permitted sender) Received: from [74.125.82.54] (HELO mail-wg0-f54.google.com) (74.125.82.54) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Dec 2013 16:29:43 +0000 Received: by mail-wg0-f54.google.com with SMTP id n12so8863665wgh.33 for ; Sat, 28 Dec 2013 08:29:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=+WMl13zt96DrM1+4jbkXpzmEI+m8pOSIeT8/uLHGOoA=; b=p7EL5Krjs3Nl3VR5tlji4A0tOIFd8YK4ho1cZAzMrbbLJE+3+sfqyPGxrKgnQU2scz T/ZQdj8KsduQNFf0Ptr8iRHkJxWr+2qMGZlU9/yoWkL3S+cib3NX8lqHb5AqfE8KnU09 UpsJ+FGDj0pBN8a0p7CXKFd37VhMMyvCOvkAIVTz9NN/3eFgKBBtvTgf9kD5oLR6BmpE NMjnu8ve6N9QnK45Ii0kF/MGlxL7YkNctZQuKizmFrR8lyae1+dmYAs3uiMF5axxegH5 p1u0/LNlDVLIg4+XovdntBJKk5R1E+9VPS+DPA+nKDLzyP8dSuiuZGWNsG8sH9lQUwBR 6A2g== X-Received: by 10.180.104.42 with SMTP id gb10mr37857757wib.51.1388248163260; Sat, 28 Dec 2013 08:29:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.92.203 with HTTP; Sat, 28 Dec 2013 08:28:43 -0800 (PST) From: =?UTF-8?Q?S=C3=A9kine_Coulibaly?= Date: Sat, 28 Dec 2013 17:28:43 +0100 Message-ID: Subject: Howto use zkCli.sh with spaces in the data ? To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=f46d041826f6a1a03f04ee9ab6ea X-Virus-Checked: Checked by ClamAV on apache.org --f46d041826f6a1a03f04ee9ab6ea Content-Type: text/plain; charset=UTF-8 I wish I could use ZooKeeper to store json data. My json data contains spaces, eg : {"country":"CA","name":"De La Salle"} Issuing the following command to zkClient only stores {"id":1,"fullname":"De which is wrong : create /contacts/1 {"country":"CA","name":"De La Salle"} The store command seems to be croped after the first space of the data payload. >From what I can see, this issuehas been raised several times (eg. here http://stackoverflow.com/questions/11408542/zookeeper-cli-read-znode-with-space and here http://zookeeper-user.578899.n2.nabble.com/Best-way-to-update-node-using-command-line-td7578581.html) but I was unable to find a better workaround than "patch the java client by yourself", so that the parameters are not splitted by a space. Are there any plans to fix this (yes, I suggest this is some kind of bug"), or a working "escaping" trick ? Thank you --f46d041826f6a1a03f04ee9ab6ea--