[
https://issues.apache.org/jira/browse/IGNITE-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-9470:
-------------------------------------
Description:
When MVCC transaction is rolled back due to a write conflict it throws
{{CacheException}} with "Mvcc version mismatch" message. This behavior violates
Ignite transactions API. Instead it should throw
{{TransactionRollbackException}} with a clear message like a "Transaction has
been aborted due to a write conflict (Please try again.)"
It is also need to propogate this changes to JDBC and ODBC components and fix
mvcc tests.
In some tests we have to repeat tx operation in case of version conflict. Most
likely, we can rely to caused-exception with some meaningful type (e.g.
MvccVersionMismatchException) to repeat operation.
was:
When MVCC transaction is rolled back due to a write conflict it throws
{{CacheException}} with "Mvcc version mismatch" message. This behavior violates
Ignite transactions API. Instead it should throw
{{TransactionRollbackException}} with a clear message like a "Transaction has
been aborted due to a write conflict (Please try again.)"
It is also need to propogate this changes to JDBC and ODBC components and fix
mvcc tests.
> MVCC TX: Mvcc transactions should throw proper exception when rolled back.
> --------------------------------------------------------------------------
>
> Key: IGNITE-9470
> URL: https://issues.apache.org/jira/browse/IGNITE-9470
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, mvcc, odbc
> Reporter: Roman Kondakov
> Assignee: Ivan Pavlukhin
> Priority: Major
> Fix For: 2.8
>
>
> When MVCC transaction is rolled back due to a write conflict it throws
> {{CacheException}} with "Mvcc version mismatch" message. This behavior
> violates Ignite transactions API. Instead it should throw
> {{TransactionRollbackException}} with a clear message like a "Transaction has
> been aborted due to a write conflict (Please try again.)"
> It is also need to propogate this changes to JDBC and ODBC components and fix
> mvcc tests.
>
> In some tests we have to repeat tx operation in case of version conflict.
> Most likely, we can rely to caused-exception with some meaningful type (e.g.
> MvccVersionMismatchException) to repeat operation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
