Vladislav Pyatkov created IGNITE-24592:
------------------------------------------
Summary: Do not send read timestamp each time when RO transaction
is used
Key: IGNITE-24592
URL: https://issues.apache.org/jira/browse/IGNITE-24592
Project: Ignite
Issue Type: Bug
Reporter: Vladislav Pyatkov
h3. Motivation
Sending a readonly timestamp has already happened in the transaction start.
Here we are sending it a second time, but the client already knows it.
{code:title=org.apache.ignite.client.handler.requests.table.ClientTableCommon#readTx}
if (tx != null && tx.isReadOnly()) {
// For read-only tx, override observable timestamp that we send to the
client:
// use readTimestamp() instead of now().
out.meta(tx.readTimestamp());
}
{code}
There is no real reason to leave this useless code.
h3. Definition of done
Remove the code where we are sending timestamps for existing RO transactions.
Ensure this change passes on TC
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
