[
https://issues.apache.org/jira/browse/IGNITE-10976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752078#comment-16752078
]
Ignite TC Bot commented on IGNITE-10976:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform C++ (Win x64 | Release){color} [[tests 2
BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2900560]]
* IgniteCoreTest: CacheQueryTestSuite: TestFieldsQueryPagesSeveral - 4,1% fails
in last 844 master runs.
* IgniteCoreTest: CacheQueryTestSuite: TestFieldsQuerySeveral - 4,1% fails in
last 844 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2899549&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC: Sql API methods should throws 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)
