[
https://issues.apache.org/jira/browse/IGNITE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503262#comment-16503262
]
Alexey Goncharuk commented on IGNITE-2313:
------------------------------------------
[~SomeFire], in this implementation this is a breaking change and will likely
affect existing users. Was there any discussion on the dev-list regarding this
change? If not, please start one, the community have to agree whether default
behavior should be to thrown an exception (new behavior) or not (existing
behavior).
My preference would be to keep the old behavior.
> 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)
