You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yakov Zhdanov (JIRA)" <ji...@apache.org> on 2015/12/29 13:44:49 UTC
[jira] [Commented] (IGNITE-2313) Need to add a mode to fail atomic
operations within a transaction
[ https://issues.apache.org/jira/browse/IGNITE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073860#comment-15073860 ]
Yakov Zhdanov commented on IGNITE-2313:
---------------------------------------
I would introduce something like {{IgniteCache.withAllowAtomicUpdatesInTx()}}. This will give us flexibility in runtime and keep us consistent with all {{.withXXX()}} stuff we have.
By default updates of atomic caches should be disabled inside txs.
Thoughts?
> 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
> Priority: Blocker
> Fix For: 1.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
(v6.3.4#6332)