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

Dmitriy Pavlov commented on IGNITE-2313:
----------------------------------------

I've checked tests, only one failure is suspicious, 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-8119706898260100446&branch=pull%2F1709%2Fhead&tab=testDetails&branch_IgniteTests24Java8=__all_branches__
 

In the same time this test was failed in other branches, so I suppose it is ok 
to proceed.

> Need to add a mode to fail atomic operations within a transaction
> -----------------------------------------------------------------
>
>                 Key: IGNITE-2313
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2313
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Dmitriy Setrakyan
>            Assignee: Ryabov Dmitrii
>            Priority: Major
>             Fix For: 2.6
>
>
> Currently atomic operations within a transaction succeed without alarming a 
> user that no transaction really occurs. We should add a mode to fail such 
> operations (such mode should be turned off by default).
> New transaction configuration flag (default is {{false}}):
> {code}TransactionConfiguration.isAllowAtomicUpdatesInTransaction(){code}
> If the flag is violated, we should throw an exception with the following 
> error message: {{Transaction spans operations on atomic cache (consider 
> setting TransactionConfiguration.isAllowAttomicUpdatesInTransaction() flag to 
> true)}}



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

Reply via email to