[JCBC-164] Support CAS for delete operation Created: 04/Dec/12 Updated: 17/Jun/13
|Project:||Couchbase Java Client|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
It would be nice if the DELETE operation would support a CAS parameter, a feature which is available in e. g. the Ruby client library. Without the possibility for checking for a given CAS value it may happen that a DELETE removes a key-value pair which was just updated by an other thread.
|Comment by Michael Nitschinger [ 04/Dec/12 ]|
Thanks for your input!
I'll discuss this and then get back to you in this ticket!
|Comment by Michael Nitschinger [ 19/Dec/12 ]|
|What do you think about this?|
|Comment by Matt Ingenthron [ 19/Dec/12 ]|
|I do think it makes sense, and it's in there actually for operations with durability requirements.|
|Comment by Ricky Martin [ 17/Jun/13 ]|
|It would be really nice, cos delete with a CAS is the only way of deleting a locked object. In my tests, under some circumstances, if the object is first unlocked and then deleted, weird things could happen (race condition). So please I need this feature in order to preserve correct locking.|