[
https://issues.apache.org/jira/browse/IGNITE-19889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-19889:
----------------------------------
Summary: Propagation of timestamp to client-side (was: Propagetion of
timestamp to client-side)
> Propagation of timestamp to client-side
> ---------------------------------------
>
> Key: IGNITE-19889
> URL: https://issues.apache.org/jira/browse/IGNITE-19889
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> *Motivation*
> Client timestamp is used to determine read timestamp for RO transaction.
> Currently, this timestamp never update, that lead to violation guaranties of
> linearization on client.
> *Implementation note*
> For commit RW transaction, use a method which return commit timestamp (the
> method is implemented in IGNITE-19886)
> Propagate commit timestamp from server to client on RW transaction commit and
> update client timestamp
> Propagate read timestamp from server to client (read timestamp for client RO
> transaction is determined in IGNITE-19888)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
