[
https://issues.apache.org/jira/browse/IGNITE-26092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-26092:
----------------------------------------
Labels: ignite-3 release-3.1.0-blocker (was: ignite-3)
> Add aipersist storage format compatibility tests
> ------------------------------------------------
>
> Key: IGNITE-26092
> URL: https://issues.apache.org/jira/browse/IGNITE-26092
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3, release-3.1.0-blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 tests have to ensure that aipersist-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 were no unmerged delta files in v1 (that is, after the writes
> are finished on v1, we wait for all delta files to be merged and removed)
> # When there were some unmerged delta-files
> # When unmerged delta-files remain from v1 and we start creating new delta
> files immediately after starting on v2, and THEN we start verifications
> listed above (while the delta files are still there)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
