Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
Mad Hatter
Description
Ambiguous result handling should be more prescriptive with how-to code samples in the following page:
https://docs.couchbase.com/server/6.5/learn/data/durability.html
The above page has general guidelines but it will be good to include sample code for handling various paths when an ambiguous result is received.
Daniel Owen FYI.
Hi Tony Hillman,
I've been talk to Daniel Roberts about what is required here and is working on some code samples to help.
The main concern is regarding non-idempotent durable writes.
In particular - we current state in the documentation
If the attempted durable write is not idempotent, the options are:
Verify the current state of the saved data; and re-attempt the durable write if appropriate.
Return an error to the user.
I thing we need code samples showing how to cope with am ambiguous result. And the gotchas associated with trying to use non-idempotent durable writes a perform tasks such as incrementing a value.
Daniel Roberts. Can you detail some of the challenges we discussed in this ticket? - thanks