[IGNITE-19898] SQL implicit RO transaction should used observation timestamp

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Done
• Fix Version/s: 3.0
• Labels: ignite-3
• Epic Link: RO transaction in past
• Assignee: Pavel Pereslegin
• Reporter: Vladislav Pyatkov
• Created: 30/Jun/23 14:04
• Updated: 04/Sep/24 16:10
• Resolved: 25/Aug/23 14:00

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.

Issue Links

• blocks: IGNITE-20232 Java client: Propagate observable timestamp to sql engine using internal API
• blocks: IGNITE-19888 Java client: Track observable timestamp
• blocks: IGNITE-19889 Implement observable timestamp on server
• blocks: IGNITE-20056 .NET: Thin 3.0: Track observable timestamp
• blocks: IGNITE-20057 C++ client: Track observable timestamp
• blocks: IGNITE-20233 jdbc: Propagate observable timestamp to sql-engine.
• is blocked by: IGNITE-19887 Transfer observable timestamp to read-only transaction
• links to: GitHub Pull Request #2449