You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Pavlukhin (JIRA)" <ji...@apache.org> on 2018/10/25 09:38:00 UTC
[jira] [Assigned] (IGNITE-9470) MVCC TX: Mvcc transactions should
throw proper exception when rolled back.
[ https://issues.apache.org/jira/browse/IGNITE-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Pavlukhin reassigned IGNITE-9470:
--------------------------------------
Assignee: Ivan Pavlukhin
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)