You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux 2.6.32-754.35.1.el6.x86_64 - OpenJDK 64-Bit Server VM 11.0.20 (Corretto-11.0.20.8.1)
Expected behavior
The manual says that using the transaction method scope lambda is equivalent to the begin/commit/rollback idiom, where the rollback occurs in case an Exception is thrown. However, in other places the manual says that in case a NeedRetryException is thrown, the transaction is automatically repeated.
Actual behavior
In the examples of a manual begin/commit/rollback sequence, the type of exception caught is Exception, which is a parent of NeedRetryException, so it seems that a retry never actually occurs.
What is the actual behaviour of the transaction method?
Steps to reproduce
N/A
The text was updated successfully, but these errors were encountered:
ArcadeDB Version:
v24.1.1 (build 48e937e/1707163239355/main)
OS and JDK Version:
Linux 2.6.32-754.35.1.el6.x86_64 - OpenJDK 64-Bit Server VM 11.0.20 (Corretto-11.0.20.8.1)
Expected behavior
The manual says that using the transaction method scope lambda is equivalent to the begin/commit/rollback idiom, where the rollback occurs in case an Exception is thrown. However, in other places the manual says that in case a NeedRetryException is thrown, the transaction is automatically repeated.
Actual behavior
In the examples of a manual begin/commit/rollback sequence, the type of exception caught is Exception, which is a parent of NeedRetryException, so it seems that a retry never actually occurs.
What is the actual behaviour of the transaction method?
Steps to reproduce
N/A
The text was updated successfully, but these errors were encountered: