[jira] [Updated] (IGNITE-15817) [Native Persistence 3.0] PageIOs abstractions porting

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

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

Sergey Chugunov updated IGNITE-15817:
-------------------------------------
    Epic Link: IGNITE-16232

> [Native Persistence 3.0] PageIOs abstractions porting
> -----------------------------------------------------
>
>                 Key: IGNITE-15817
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15817
>             Project: Ignite
>          Issue Type: Task
>          Components: persistence
>            Reporter: Sergey Chugunov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0
>
>
> h2. Goal
> We want to keep PageIO abstraction in general but refine it, address some flaws and repay tech debt that has built up in this subsystem.
> h2. Items to pay attention to
> Abstract parent PageIO class is overloaded with functionality (bad smell from static methods etc), responsibilities split and minor redesign is needed.
> Retrieving version of a particular page requires complicated machinery, it should be simplified.
> PageMetaIO hierarchy flattening - responsibilities of intermediate classes should be unified and grouped in a lower hierarchy.
> Old versions cleanup: versions history shrinking is safe as no binary compatibility between 2.x and 3.0.
> Reconsider approaches to support versioning and binary compatibility. Classes with names like V2, V3 look questionable, we may come up with other naming or completely different approach.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)