[IGNITE-23110] Disallow IgniteCache#clear inside transaction

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 2.17
• Labels: ise
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Julia Bakulina
• Reporter: Nikolay Izhikov
• Created: 29/Aug/24 11:43
• Updated: 02/Sep/24 08:49

Description

`IgniteCache#clear` invocation are not transactional.
But, currently, Ignite allow to invoke `clear` inside transaction.
This lead to unexpected behavior and hides business logic errors.

We must disallow IgniteCache#clear call inside transaction.

/** */
@Test
public void testClearInTransction() {
    IgniteCache<Object, Object> cache = client.createCache(new CacheConfiguration<>("my-cache").setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL));
    cache.put(1, 1);
    try (Transaction tx = client.transactions().txStart(TransactionConcurrency.PESSIMISTIC, TransactionIsolation.READ_COMMITTED)) {
        cache.put(2, 2);
        cache.clear();
        tx.commit();
    }
    assertFalse(cache.containsKey(1));
    assertTrue(cache.containsKey(2));
}

Issue Links

• is cloned by: IGNITE-23121 CLONE - Disallow IgniteCache#iterator inside transaction
• relates to: IGNITE-8801 Change default behaviour of atomic operations inside transactions
• relates to: IGNITE-2313 Need to add a mode to fail atomic operations within a transaction
• relates to: IGNITE-20579 Finally restrict atomic operations inside the transaction (remove the system property)