Couchbase Java Client

Support CAS for delete operation

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.1-beta
  • Fix Version/s: 1.1.8
  • Component/s: library
  • Security Level: Public
  • Labels:
    None

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.

Issue Links

is duplicated by

Improvement - An improvement or enhancement to an existing feature or task. JCBC-193 Allow CAS with delete

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Michael Nitschinger added a comment -
Thanks for your input!

I'll discuss this and then get back to you in this ticket!
Show
Michael Nitschinger added a comment - Thanks for your input! I'll discuss this and then get back to you in this ticket!
Hide
Permalink
Michael Nitschinger added a comment -
What do you think about this?
Show
Michael Nitschinger added a comment - What do you think about this?
Hide
Permalink
Matt Ingenthron added a comment -
I do think it makes sense, and it's in there actually for operations with durability requirements.
Show
Matt Ingenthron added a comment - I do think it makes sense, and it's in there actually for operations with durability requirements.
Hide
Permalink
Ricky Martin added a comment -
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.
Show
Ricky Martin added a comment - 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.

People

  • Assignee:
    Michael Nitschinger
    Reporter:
    schp
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:

Agile