You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2024/11/05 07:37:00 UTC

[jira] [Created] (IGNITE-23603) Implicit transaction for direct RO read

Vladislav Pyatkov created IGNITE-23603:
------------------------------------------

             Summary: Implicit transaction for direct RO read
                 Key: IGNITE-23603
                 URL: https://issues.apache.org/jira/browse/IGNITE-23603
             Project: Ignite
          Issue Type: Improvement
            Reporter: Vladislav Pyatkov


h3. 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:
{code}
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)
{code}

h3. 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).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)