[
https://issues.apache.org/jira/browse/IGNITE-22086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842305#comment-17842305
]
Pavel Tupitsyn commented on IGNITE-22086:
-----------------------------------------
Merged to main:
[66172ffc2c07ebc13d25f496b54768eb718dad09|https://github.com/apache/ignite-3/commit/66172ffc2c07ebc13d25f496b54768eb718dad09]
> Thin 3.0: observableTimestamp is 0 after handshake
> --------------------------------------------------
>
> Key: IGNITE-22086
> URL: https://issues.apache.org/jira/browse/IGNITE-22086
> Project: Ignite
> Issue Type: Bug
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We propagate *observableTimestamp* to client with every response (see
> *ClientInboundMessageHandler#writeResponseHeader*), but not on handshake. As
> a result, the very first operation from the client has
> *observableTimestamp=0*, which can lead to causality issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
