ptupitsyn commented on issue #12639:
URL: https://github.com/apache/ignite/issues/12639#issuecomment-3772059413
For what it's worth, below is a workaround using the internal API to pass
around the "causality token" or "observable timestamp":
```java
// Sender service gets timestamp after doing updates
TcpIgniteClient senderTcpClient = (TcpIgniteClient) igniteClient;
long ts =
senderTcpClient.channel().observableTimestamp().get().longValue(); // Include
ts in the REST call
// Receiver service gets sender timestamp from REST call and applies:
long senderTs = ...;
TcpIgniteClient receiverTcpClient = (TcpIgniteClient) igniteClient;
receiverTcpClient.channel().observableTimestamp().update(ts);
// Now read the data, transaction is not necessary
```
(add a dependency to `org.apache.ignite:ignite-core` to make it work)
@malte-f19 thank you for raising this issue, it triggered an important
discussion with the team, hopefully we will make this better in the next
release.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
