[
https://issues.apache.org/jira/browse/IGNITE-20322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-20322:
----------------------------------
Description:
*Motivation*
An implicit transaction is a transaction that is started by the table API when
a single operation is executed and committed when the operation is finished.
Currently, implicit transactions use the common observable timestamp. The
timestamp is reserved for transactions started by the embedded node only. That
leads to unnecessary adjustments of the observable timestamp (the timestamp is
updated more often than required), that may have serious performance impact on
read-only transactions and read operations which use implicit read-only
transactions.
*Definition of done*
Implicit transactions should start with an observable timestamp that is
specific for each embedded server or for each client.
was:
*Motivation*
An implicit transaction is a transaction that is started by the table API when
a single operation is executed and committed when the operation is finished.
Currently, internal transactions use the only observable timestamp. The
timestamp is reserved for embedded transactions only. That leads to incorrect
calculations of the observable timestamp (the timestamp is updated more
frequently than required).
*Definition of done*
Implicit transactions should start with a specific observable timestamp (for
the embedded server or for each client).
> Add ability to pass an observable timestamp to an implicit transaction
> ----------------------------------------------------------------------
>
> Key: IGNITE-20322
> URL: https://issues.apache.org/jira/browse/IGNITE-20322
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> *Motivation*
> An implicit transaction is a transaction that is started by the table API
> when a single operation is executed and committed when the operation is
> finished. Currently, implicit transactions use the common observable
> timestamp. The timestamp is reserved for transactions started by the embedded
> node only. That leads to unnecessary adjustments of the observable timestamp
> (the timestamp is updated more often than required), that may have serious
> performance impact on read-only transactions and read operations which use
> implicit read-only transactions.
> *Definition of done*
> Implicit transactions should start with an observable timestamp that is
> specific for each embedded server or for each client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
