DATA QUALITY: Please support graph transactions.
Today, if a traversal fails at step n of m, figuring out what state the graph is in is quite a chore. As a result, all data modification traversals have to be written to support retries. Unfortunately, if the retrying component fails, the network fails, or something else fails, which prevents retry, the graph is left in an unknown state.
Hello and thank you for your suggestion.
While Cosmos DB provides support for transactions within a partition, we do not have support multi-step, cross-partition or distributed transactions.
We recommend to customers requiring transactions across multi-step operations to coordinate these using the consistency model and optimistic concurrency control.
Thank you for your suggestion.
Thanks for getting back to me here, please may you provide an example using the Gremlin.NET API, which shows us how to do this? If we could get partition transactions working that'd be awesome for our app.