Vladislav Pyatkov created IGNITE-18194:
------------------------------------------
Summary: Scan chooses incorerect timestamp to scan storage in RO
transaction
Key: IGNITE-18194
URL: https://issues.apache.org/jira/browse/IGNITE-18194
Project: Ignite
Issue Type: Improvement
Reporter: Vladislav Pyatkov
*Motivation:*
Method _PartitionReplicaListener.retrieveExactEntriesUntilCursorEmpty_ creates
a cursor over storage using _HybridTimestamp.MAX_VALUE_ timestamp, but required
to use a timestamp from request (_readTimestamp_ is a timestamp from read
request here).
Also, this scenario is not covered by test, because TC is green. Need to write
a test scenario that demonstrate issue when storage cursor is opened with
incorrect timestamp in RO transaction.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
