Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: domain of cf@renttherunway.com
 designates 209.85.215.43 as permitted sender)
MIME-Version: 1.0
Sender: cf@renttherunway.com
In-Reply-To: <etPan.539ef39c.1e7ff521.11c@Jordans-MacBook-Pro.local>
References: <5B18D739-E881-408A-B5E1-B0F4DB7339B8@gmail.com>
	<etPan.539ef39c.1e7ff521.11c@Jordans-MacBook-Pro.local>
Date: Mon, 16 Jun 2014 09:41:46 -0400
Message-ID: 
 <CAKF1A=uMqLA0F=Jro-r5U4GHD=r6JsewXCUZ0_7cHX8rk-_6ZA@mail.gmail.com>
Subject: Re: renaming a znode
From: Camille Fournier <camille@apache.org>
To: "bookkeeper-user@zookeeper.apache.org" <user@zookeeper.apache.org>
Cc: Mudit Verma <mudit.f2004912@gmail.com>
Content-Type: multipart/alternative; boundary=089e013d1c4c3ed4bf04fbf430a7

--089e013d1c4c3ed4bf04fbf430a7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Just to clarify you mean the multi API?
C
On Jun 16, 2014 9:40 AM, "Jordan Zimmerman" <jordan@jordanzimmerman.com>
wrote:

> You could use the transaction api to create a new node and delete the old
> node.
>
> -JZ
>
>
> From: Mudit Verma mudit.f2004912@gmail.com
> Reply: user@zookeeper.apache.org user@zookeeper.apache.org
> Date: June 16, 2014 at 8:38:11 AM
> To: user@zookeeper.apache.org user@zookeeper.apache.org
> Subject:  renaming a znode
>
> Hello People,
>
> Sorry for asking many questions these days. :)
>
> I am wondering if it is possible to rename a znode? I am building a
> distributed map on top of zookeeper for special needs. From time to time,=
 I
> need to freeze the map without restricting write access to the map.
>
> I plan to do it by maintaining two maps:
>
> map_current
> map_frozen
>
> all the map entries are maintained as separate children znodes where key
> is the name of the child node and value is the value stored on the child
> node ..
> for example /map_current/entry1(kv)
> /map_current/entry2(kv)
>
>
> Now at some point of time, I need to iterate the map while still allowing
> write access by other clients. While I iterate, I don=E2=80=99t want othe=
r clients
> to see these entries. Once I process map_frozen entries I will delete the=
m
> (I don=E2=80=99t need them anymore) by just deleting the parent node.
>
> I plan to rename existing map from map_current to map_frozen and create
> new map as map_current with empty data for further writes. Other clients
> will continue to write new entries in map_current .. so on so forth ..
>
> Any suggestions on how can I do it efficiently.
>
> Thanks
> Mudit

--089e013d1c4c3ed4bf04fbf430a7--