You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2022/10/12 14:20:00 UTC

[jira] [Assigned] (IGNITE-17864) Optimize scan(HybridTimestamp.MAX_VALUE) and read(HybridTimestamp.MAX_VALUE)

     [ https://issues.apache.org/jira/browse/IGNITE-17864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Puchkovskiy reassigned IGNITE-17864:
------------------------------------------

    Assignee: Roman Puchkovskiy

> 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
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>
> 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)