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 2019/02/01 14:44:00 UTC

[jira] [Updated] (IGNITE-10976) MVCC: Sql API methods should throw proper TransactionExceptions in case of tx failure.

     [ https://issues.apache.org/jira/browse/IGNITE-10976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Pavlukhin updated IGNITE-10976:
------------------------------------
    Summary: MVCC: Sql API methods should throw proper TransactionExceptions in case of tx failure.  (was: MVCC: Sql API methods should throws proper TransactionExceptions in case of tx failure.)

> MVCC: Sql API methods should throw proper TransactionExceptions in case of tx failure.
> --------------------------------------------------------------------------------------
>
>                 Key: IGNITE-10976
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10976
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc, sql
>            Reporter: Andrew Mashenkov
>            Assignee: Andrew Mashenkov
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> For now Sql API can throws SqlException (without any actual Tx failure cause) or TransactionException wrapped into CacheException.
> Also, I've found we convert unchecked exceptions into checked ones and then back without any obvious reason.
> Let's make TransactionException thows properly and add it to Sql Api contract.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)