[
https://issues.apache.org/jira/browse/IGNITE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108600#comment-16108600
]
Ryabov Dmitrii edited comment on IGNITE-2313 at 8/1/17 9:01 AM:
----------------------------------------------------------------
Thx for review, [~sboikov]. I added test to basic suite, more methods to test
and replaced tx check as you said. Also I merged master to my branch, so it
also have 30+ failed tests in TeamCity [1].
[1]
http://ci.ignite.apache.org/viewLog.html?buildId=748884&tab=buildResultsDiv&buildTypeId=Ignite20Tests_RunAll
was (Author: somefire):
Thx for review, [~sboikov]. I added test to basic suite, more methods to test
and replaced tx check as you said. Also I merged master to my branch, so it
also have 30+ failed tests in TeamCity.
> 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
> Fix For: 2.2
>
>
> 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
(v6.4.14#64029)
