[ https://issues.apache.org/jira/browse/IGNITE-19898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-19898: ------------------------------------ Description: *Motivation* Reorganization of processing of RO transaction requires choosing a specific timestamp for an implicit RO SQL transaction. *Implementation notes* * Observable timestamp is passed through API and propagate to SQL engine. * SQL uses the observable timestamp when it has to start RO transaction (IGNITE-19887 is used to start RO transaction with specified observable timestamp). * Read timestamp, that is got through transaction API {{ReadOnlyTransactionImpl#readTimestamp}}, should to be available for invoking side. *Definition of done* * Select in an implicit transaction should execute with an observable timestamp (see TODO in *ClientSqlExecuteRequest*). A read timestamp, which is used for RO transaction calculation, returns to the invoking side. was: *Motivation* Reorganization of processing of RO transaction requires choosing a specific timestamp for an implicit RO SQL transaction. *Implementation notes* * Observable timestamp is passed through API and propagate to SQL engine. * SQL uses the observable timestamp when it has to start RO transaction (IGNITE-19887 is used to start RO transaction with specified observable timestamp). * Read timestamp, that is got through transaction API {{ReadOnlyTransactionImpl#readTimestamp}}, should to be available for invoking side. *Definition of done* * Select in an implicit transaction should execute with an observable timestamp. A read timestamp, which is used for RO transaction calculation, returns to the invoking side. * See TODO in *ClientSqlExecuteRequest* > SQL implicit RO transaction should used observation timestamp > ------------------------------------------------------------- > > Key: IGNITE-19898 > URL: https://issues.apache.org/jira/browse/IGNITE-19898 > Project: Ignite > Issue Type: Improvement > Reporter: Vladislav Pyatkov > Priority: Major > Labels: ignite-3 > > *Motivation* > Reorganization of processing of RO transaction requires choosing a specific > timestamp for an implicit RO SQL transaction. > *Implementation notes* > * Observable timestamp is passed through API and propagate to SQL engine. > * SQL uses the observable timestamp when it has to start RO transaction > (IGNITE-19887 is used to start RO transaction with specified observable > timestamp). > * Read timestamp, that is got through transaction API > {{ReadOnlyTransactionImpl#readTimestamp}}, should to be available for > invoking side. > *Definition of done* > * Select in an implicit transaction should execute with an observable > timestamp (see TODO in *ClientSqlExecuteRequest*). A read timestamp, which is > used for RO transaction calculation, returns to the invoking side. -- This message was sent by Atlassian Jira (v8.20.10#820010)