[IGNITE-12622] Forbid mixed cache groups with both atomic and transactional caches

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: cache
• Labels: IEP-80 newbie
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Ivan Rakov
• Created: 05/Feb/20 07:56
• Updated: 27/May/24 13:29

Description

Apparently it's possible in Ignite to configure a cache group with both ATOMIC and TRANSACTIONAL caches.
IgniteCacheGroupsTest#testContinuousQueriesMultipleGroups* tests.
As per discussed on dev list (http://apache-ignite-developers.2346864.n4.nabble.com/Forbid-mixed-cache-groups-with-both-atomic-and-transactional-caches-td45586.html), the community has concluded that such configurations should be prohibited.

Forbidden at IGNITE-20575
IGNITE-20623 should be fixed prior this fix.

Issue Links

• blocks: IGNITE-22344 Tx counters refactoring
• is blocked by: IGNITE-20623 Avoid mixed cache groups at datastructures (IgniteSet, IgniteQueue, etc)
• is related to: IGNITE-12854 Node failed under load when ATOMIC and TRANSACTIONAL caches created in the same cache group
• relates to: IGNITE-2313 Need to add a mode to fail atomic operations within a transaction
• requires: IGNITE-20575 Forbid mixed cache groups with both atomic and transactional caches (with system property able to allow)