[
https://issues.apache.org/jira/browse/IGNITE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523647#comment-16523647
]
Anton Vinogradov commented on IGNITE-2313:
------------------------------------------
[~dpavlov],
No, because this code created to become a part of 3.0.
It is not good idea to restrict atomic ops now, this can cause issues at
customers deployments.
Currently we allow atomic ops, but already restricted them at tests.
So, allow() now useful at tests.
At 3.0 we'll disable atomic ops by default.
So, there is no need to have disallow() method.
> 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)
