You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2023/06/30 10:38:00 UTC

[jira] [Updated] (IGNITE-19887) Add API to get read timestamp for standalone server node

     [ https://issues.apache.org/jira/browse/IGNITE-19887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Tupitsyn updated IGNITE-19887:
------------------------------------
    Summary: Add API to get read timestamp for standalone server node  (was: Add a method to get read timestamp for standalone server node)

> Add API to get read timestamp for standalone server node
> --------------------------------------------------------
>
>                 Key: IGNITE-19887
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19887
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>
> *Motivation*
> RO transaction has timestamp which determine a moment when data will be read. To avoid waiting, safe time is supposed to provide the timestamp in the past. The timestamp is determined by the last committed transaction on this server in order to be available to retrieve all data which is locally fixed.
> *Implementation notes*
> * The last commit timestamp should save and update in {{TxManagerImpl}} during any transaction committed.
> * Read timestamp is determined as {{max(lastCommitTimestamp, now() - safeTimePropagationFrequency)}} by default
> * Add a new method to start read only transaction with specific timestamp:
> {code}
> /**
>  * Starts a readonly transaction with specific timestamp.
>  *
>  * @param readTimestamp Read timestamp.
>  * @return Reade only transaction.
>  */
> public ReadOnlyTransactionImpl begin(HybridTimestamp readTimestamp)
> {code}



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