[
https://issues.apache.org/jira/browse/IGNITE-8801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julia Bakulina updated IGNITE-8801:
-----------------------------------
Description:
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.
was:
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 decided during Ignite Dev List discussion as of 18/10/2022, we need to break
changes of IGNITE-8801 into 2 steps:
1) deprecate IGNITE_ALLOW_ATOMIC_OPS_IN_TX system property during the next
release - IGNITE-17916;
2) delete this property in the release after the next one - IGNITE-8801.
As per the latest round of discussion on Ignite Dev List as of 28/10/2022:
> 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: 40m
> 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)
