Consider adding an "execute" method to the Terrastore client's UpdateOperation.
This would be functionally similar to the existing executeAndGet, except... it
wouldn't get. :)
For update operations where the client is not interested in receiving the
updated document (e.g., writing or updating entries in a work log of sorts),
this could avoid some network traffic.
Original issue reported on code.google.com by teonanac...@gmail.com on 21 Feb 2011 at 1:27
Original issue reported on code.google.com by
teonanac...@gmail.com
on 21 Feb 2011 at 1:27