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

Vladislav Pyatkov updated IGNITE-19889:
---------------------------------------
    Description: 
*Motivation*
Client timestamp is used to determine a read timestamp for RO transaction on 
client-side (IGNITE-19888). For consistency behavior, need to implement a 
similar timestamp on server.

*Implementation note*
The last server observable timestamp should update at least when the 
transaction commuted.
Any RO transaction should use the timestamp: for SQL (IGNITE-19898) and through 
key-value API (IGNITE-19887)

Definition of done:
All serve-side created RO transaction should execute in past with timestamp has 
been determining by last observation time.

  was:
*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)


> Implement last oservable timestamp for server
> ---------------------------------------------
>
>                 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 a read timestamp for RO transaction on 
> client-side (IGNITE-19888). For consistency behavior, need to implement a 
> similar timestamp on server.
> *Implementation note*
> The last server observable timestamp should update at least when the 
> transaction commuted.
> Any RO transaction should use the timestamp: for SQL (IGNITE-19898) and 
> through key-value API (IGNITE-19887)
> Definition of done:
> All serve-side created RO transaction should execute in past with timestamp 
> has been determining by last observation time.



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

Reply via email to