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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8
• Component/s: mvcc, sql
• Assignee: Andrey Mashenkov
• Reporter: Andrey Mashenkov
• Created: 18/Jan/19 11:19
• Updated: 20/Feb/19 11:57
• Resolved: 04/Feb/19 10:09

Description

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.

Issue Links

• blocks: IGNITE-11152 IgniteTxManager.idMap possible memory leak
• is related to: IGNITE-9470 MVCC TX: Mvcc transactions should throw proper exception.
• is related to: IGNITE-10415 MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.
• relates to: IGNITE-10377 MVCC: Incorrect exception is thrown if no data nodes found for a partition.
• requires: IGNITE-10377 MVCC: Incorrect exception is thrown if no data nodes found for a partition.
• links to: GitHub Pull Request #5870