Update operations should provide the option to avoid returning the updated document

byzhang / terrastore

Automatically exported from code.google.com/p/terrastore

Other

0 stars 0 forks source link

Update operations should provide the option to avoid returning the updated document #162

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago

Accepted, but lower priority IMHO.

Original comment by sergio.b...@gmail.com on 21 Feb 2011 at 6:32

Changed title: Update operations should provide the option to avoid returning the updated document
Changed state: Accepted
Added labels: Priority-Low

GoogleCodeExporter commented 9 years ago

Original comment by sergio.b...@gmail.com on 21 Feb 2011 at 6:33

Added labels: Project-Terrastore, Project-Terrastore-JavaClient, Type-Enhancement