[IGNITE-8801] Change default behaviour of atomic operations inside transactions

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.15
• Labels: ise

Release Note

IGNITE_ALLOW_ATOMIC_OPS_IN_TX turned false by default. To return the previous behaviour and to allow transactions in operations with atomic caches set
IGNITE_ALLOW_ATOMIC_OPS_IN_TX to true in IgniteSystemProperties

• Ignite Flags: Release Notes Required
• Assignee: Julia Bakulina
• Reporter: Ryabov Dmitrii
• Created: 14/Jun/18 14:51
• Updated: 5 days ago 22:23
• Resolved: 01/Dec/22 07:59

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.

Issue Links

• incorporates: IGNITE-17916 Deprecate IGNITE_ALLOW_ATOMIC_OPS_IN_TX system property
• is related to: IGNITE-2313 Need to add a mode to fail atomic operations within a transaction
• is related to: IGNITE-23110 Disallow IgniteCache#clear inside transaction
• relates to: IGNITE-2313 Need to add a mode to fail atomic operations within a transaction
• links to: Devlist discssion
• links to: GitHub Pull Request #4304
• links to: GitHub Pull Request #4304
• links to: GitHub Pull Request #10318