[
https://issues.apache.org/jira/browse/IGNITE-17864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-17864:
-------------------------------------
Description: Please check
https://issues.apache.org/jira/browse/IGNITE-17856 for more details about
scan(UUID txId) and read(RowId rowId, UUID txId) removal. Within given ticket
it's expected that timestamp based scans and reads will be optimized in order
to perform HybridTimestamp.MAX_VALUE bouned operations in a most efficient way.
(was: Please check https://issues.apache.org/jira/browse/IGNITE-17856 for more
details about scan(UUID txId) and read(RowId rowId, UUID txId) removal. Within
given ticket it's expected that timestamp based scans will be optimized in
order to perform)
> Optimize scan(HybridTimestamp.MAX_VALUE) and read(HybridTimestamp.MAX_VALUE)
> ----------------------------------------------------------------------------
>
> Key: IGNITE-17864
> URL: https://issues.apache.org/jira/browse/IGNITE-17864
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Priority: Major
>
> Please check https://issues.apache.org/jira/browse/IGNITE-17856 for more
> details about scan(UUID txId) and read(RowId rowId, UUID txId) removal.
> Within given ticket it's expected that timestamp based scans and reads will
> be optimized in order to perform HybridTimestamp.MAX_VALUE bouned operations
> in a most efficient way.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
