ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2313) Need to add a mode to fail atomic operations within a transaction
Date Wed, 13 Jun 2018 15:00:00 GMT

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

Alexey Goncharuk commented on IGNITE-2313:

[~SomeFire], unfortunately, the fix did not make in Ignite 2.0 timeframe and now it makes
a breaking change for current Ignite users. 

I will bump up the discussion to check in with community regarding this change.

> 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

View raw message