[JCBC-164] Support CAS for delete operation Created: 04/Dec/12 Updated: 17/Jun/13 |
|
| Status: | Open |
| Project: | Couchbase Java Client |
| Component/s: | library |
| Affects Version/s: | 1.1-beta |
| Fix Version/s: | 1.1.8 |
| Security Level: | Public |
| Type: | New Feature | Priority: | Major |
| Reporter: | schp | Assignee: | Michael Nitschinger |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
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.
|
| Comments |
| 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. |