[
https://issues.apache.org/jira/browse/IGNITE-19889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-19889:
-----------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> Implement observable timestamp on server
> ----------------------------------------
>
> Key: IGNITE-19889
> URL: https://issues.apache.org/jira/browse/IGNITE-19889
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> *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 transactions should execute in past with timestamp
> has been determining by last observation time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
