[jira] [Updated] (IGNITE-16697) [Versioned Storage] POC - add methods for versioned data storage

["Sergey Chugunov (Jira)" <ji...@apache.org>]

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

Sergey Chugunov updated IGNITE-16697:
-------------------------------------
    Epic Link: IGNITE-16923

> [Versioned Storage] POC - add methods for versioned data storage
> ----------------------------------------------------------------
>
>                 Key: IGNITE-16697
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16697
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Bessonov
>            Assignee: Ivan Bessonov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha5
>
>          Time Spent: 10h 20m
>  Remaining Estimate: 0h
>
> As a first step towards MV-storage in Ignite 3.0 it's required to have specific methods on the partition storage and index storage interfaces. These will replace currently available VersionedRowStore, which was a prototype in itself and doesn't correspond to a desired functionality.
> Partition storage needs:
>  * addWrite(k, v, txId)
>  * commitWrite(k, ts)
>  * abortWrite(k)
>  * read(k, ts)
>  * scan(ts, {_}tbd{_})
>  * cleanup({_}tbd{_})
> Sorted index storage needs:
>  * scan(lower, upper, bounds_options, projection, partition_filter, ts)
> Index updates will be hidden inside of {*}addWrite{*}, *abortWrite* and *cleanup* methods. No external "update" and "remove" are required.
> This particular issue is a precursor for the https://issues.apache.org/jira/browse/IGNITE-16611.
> Reference implementation is also required, it'll provide an example of what's expected from the storage and a set of tests to fix methods contracts.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)