[
https://issues.apache.org/jira/browse/IGNITE-18194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685914#comment-17685914
]
Vladislav Pyatkov commented on IGNITE-18194:
--------------------------------------------
Merged d7d5050fbab5f73468c1ba44bb4b4f249eb58c3d
> Scan chooses incorrect 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
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> h3. 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.
> h3. Implementation Notes
> >>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.
> Seems that we already have such test
> org.apache.ignite.internal.table.TxAbstractTest#testReadOnlyGetWriteIntentResolutionUpdate
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
