You can simulate this using multi transactions in the current system. I think the transactionality of move in the way you are suggesting breaks down to a multi transaction, so implementing it as a special api call may be considered redundant.
C On Thu, Nov 15, 2012 at 2:14 PM, Robin Bate Boerop < [email protected]> wrote: > Zookeeper users, > > Has anyone investigated the implementation of a 'move' operation in > Zookeeper? > > For example, suppose that a node '/x/y/z' has 50 Ko of data associated > with it. A client wants the same data to be found only in node '/a/b/c'. > The client must: > 1. Get the contents of '/x/y/z', incurring a transfer of the 50 Ko of data > from ZK. > 2. Create node '/a/b/c' with the same 50 Ko of data, incurring another > transfer of it. > 3. Delete node '/x/y/z'. > > It would be simpler to issue a 'move' command: move('/x/y/z', '/a/b/c'). > This would also be much faster. > > -- > Robin Bate Boerop >
