You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Julia Bakulina (Jira)" <ji...@apache.org> on 2022/12/01 08:07:00 UTC

[jira] [Commented] (IGNITE-8801) Change default behaviour of atomic operations inside transactions

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

Julia Bakulina commented on IGNITE-8801:
----------------------------------------

[~timonin.maksim] thank you for the review

> Change default behaviour of atomic operations inside transactions
> -----------------------------------------------------------------
>
>                 Key: IGNITE-8801
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8801
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Ryabov Dmitrii
>            Assignee: Julia Bakulina
>            Priority: Minor
>              Labels: ise
>             Fix For: 2.15
>
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> Need to change default behaviour of atomic operations to fail inside transactions.
> 1) Remove IGNITE_ALLOW_ATOMIC_OPS_IN_TX system property.
> 2) Set default value to restrict atomic operations in {{CacheOperationContext}} constructor without arguments and arguments for calls of another constructor.
> 3) Fix javadocs.
> As per the latest round of discussion on Ignite Dev List as of 28/10/2022 we agreed on the following:
> 1) Revert deprecation IGNITE-17916 - reverted
> 2) Change default value in 2.15.
> 3) Notify users in release notes, an exception message - how to change the
> behavior back.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)