With the latest versions of Couchbase and Couchbase SDKs, support for transactions has been provided for both N1QL Statements as well as KV Ops.
What is the current state of support for transactions within the Eventing service on the latest version of couchbase? If not supported, is it on the roadmap? or is it generally advised to make a CURL to an internal API that can facilitate that transaction business logic there.
Hey Alex one thing to be aware of in Eventing transactions “begin work”, “commit work”, and “rollback work” currently can “leak” some unexpected mutations so that you might get extra document(s) that are unexpected on a update/insert or on a delete so you have to be very careful about when you use transactions and eventing together.
Of course we plan to fix this but there is no definitive roadmap or release time for this I’m pushing to get it fixed sooner than later hope this helps.
What do you mean by “leak” unexpected mutations?
As in, eventing may pick up the uncommitted transaction state and process the mutation?
Also, are there any solutions for KV and transactions? Looks like the solution provided are for DML Query Statements Only. SDKs have the ability to perform both KV and Query operations within a ctx context.