[
https://issues.apache.org/jira/browse/IGNITE-25902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018389#comment-18018389
]
Vladislav Pyatkov commented on IGNITE-25902:
--------------------------------------------
This method has two disadvantages:
# We cannot use an instant timestamp as a read-only timestamp, because
internally we are using a hybrid timestamp (with a logical part).
# The property is a part of the transaction, but in a client transaction the
timestamp is initiated on the server side.
> Add transaction read timestamp to public API
> --------------------------------------------
>
> Key: IGNITE-25902
> URL: https://issues.apache.org/jira/browse/IGNITE-25902
> Project: Ignite
> Issue Type: Improvement
> Components: ro transactions ai3, transactions ai3
> Reporter: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.1
>
>
> Add the following to the *Transaction* interface:
> {code:java}
> /**
> * Returns the read timestamp of the read-only transaction, or {@code null}
> if the transaction is not read-only.
> *
> * <p>Read-only transactions provide a snapshot view of data at a point in
> time represented by this timestamp.
> *
> * @return The timestamp of the transaction.
> */
> @Nullable Instant readTimestamp();
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
