[
https://issues.apache.org/jira/browse/IGNITE-26094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-26094:
---------------------------------------
Description:
Legend: v1 is original version (3.0), v2 is current version (version from main
branch).
It is supposed that data is written in v1, then the storage is flushed and the
node is stopped, its binary is replaced with v2, the node is started.
The test must ensure that rocksdb-based tables work correctly:
# all data written in v1 can be read in v2
# including overwritten versions
# deleted data cannot be read
# updates that are rolled back cannot be read
was:
Legend: v1 is original version (3.0), v2 is current version (version from main
branch).
It is supposed that data is written in v1, then the storage is flushed and the
node is stopped, its binary is replaced with v2, the node is started.
The test must ensure that rocksdb-based tables work correctly:
# all data written in v1 can be read in v2
# including overwritten versions
# deleted data cannot be read
# updates that are rolled back cannot be read
Here are variations that need to be tested:
# When there are just L0
> Add rocksdb storage format compatibility tests
> ----------------------------------------------
>
> Key: IGNITE-26094
> URL: https://issues.apache.org/jira/browse/IGNITE-26094
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> Legend: v1 is original version (3.0), v2 is current version (version from
> main branch).
> It is supposed that data is written in v1, then the storage is flushed and
> the node is stopped, its binary is replaced with v2, the node is started.
> The test must ensure that rocksdb-based tables work correctly:
> # all data written in v1 can be read in v2
> # including overwritten versions
> # deleted data cannot be read
> # updates that are rolled back cannot be read
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
