Transaction Exceptions and Retries
It's a common pattern for database drivers/clients to have specialized exceptions for failed transactions that provide the necessary context for knowing whther or not to retry the exception due to conflicts.
Does Tinkerpop have any of this? Right now basically it seems like users need to unpack the layers of the exceptions that the server feeds back to the client, and then just string parse completely based off of a string the graph provider tells them to look for (if there even is one) in order to do this very common-used pattern with transactions in a database.
Does Tinkerpop have any of this? Right now basically it seems like users need to unpack the layers of the exceptions that the server feeds back to the client, and then just string parse completely based off of a string the graph provider tells them to look for (if there even is one) in order to do this very common-used pattern with transactions in a database.
Apache TinkerPop is an open source graph computing framework and the home of the Gremlin graph query language.
1,376Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
