Pavel Tupitsyn created IGNITE-26555:
---------------------------------------
Summary: Inconsistent read-only transaction timestamp behavior in
embedded and client modes
Key: IGNITE-26555
URL: https://issues.apache.org/jira/browse/IGNITE-26555
Project: Ignite
Issue Type: Bug
Components: thin clients ai3
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 3.2
* In embedded mode, *TxManagerImpl.beginReadOnlyTransaction* immediately
retrieves current *observableTimestamp* to calculate *readTimestamp*
* In client mode, *ClientLazyTransaction* retrieves *observableTimestamp* from
the tracker only in *ensureStarted* when the first transactional operation is
performed.
As a result, the same user code will behave differently with embedded and
client APIs:
{code}
var tx = transactions.begin(readOnly = true);
view.upsert(null, tuple1);
// Fails on client, succeeds on server
assert view.get(tx, tuple1) == null;
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
