[IGNITE-23603] Implicit transaction for direct RO read

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: ignite-3
• Epic Link: RO transaction in past
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Vladislav Pyatkov
• Created: 05/Nov/24 07:36
• Updated: 05/Nov/24 08:05

Description

Motivation

We are creating an implicit transaction through an internal API (IgniteTransactionsImpl#beginImplicit). It is needed to distinguish observation timestamps for multiple clients and embedded mode.
Unfortunately, this API is useless to create a direct RO transaction because their logic works only if incomming transaction is null:

InternalTableImpl#get(org.apache.ignite.internal.schema.BinaryRowEx, org.apache.ignite.internal.tx.InternalTransaction)
InternalTableImpl#getAll(java.util.Collection<org.apache.ignite.internal.schema.BinaryRowEx>, org.apache.ignite.internal.tx.InternalTransaction)

Definition of done

Add a possibility to create an implicit transaction for the RO direct.
This approach will be able to be used in ClientTupleGetAllRequest and ClientTupleGetRequest (I left TODOs there).

Issue Links

• is blocked by: IGNITE-20322 Add ability to pass an observable timestamp to an implicit transaction