ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9470) MVCC TX: Mvcc transactions should throw proper exception when rolled back.
Date Thu, 28 Feb 2019 13:53:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780536#comment-16780536

Ignite TC Bot commented on IGNITE-9470:

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3199880&amp;buildTypeId=IgniteTests24Java8_RunAll]

> 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
>              Labels: Muted_test, mvcc_stabilization_stage_1, transactions
>             Fix For: 2.8
>          Time Spent: 10m
>  Remaining Estimate: 0h
> 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.
> Pay attention that tx could be aborted at different stages, but we should fail consistently.
Some examples:
> 1. Before next operation in tx started.
> 2. While operation in tx is in progress.
> 3. When {{tx.commit()}} is called.

This message was sent by Atlassian JIRA

View raw message