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

Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2024/03/13 09:25:00 UTC

[jira] [Commented] (IGNITE-21742) Refactor creating and managing of Page Memory Indexes

    [ https://issues.apache.org/jira/browse/IGNITE-21742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825978#comment-17825978 ] 

Kirill Tkalenko commented on IGNITE-21742:
------------------------------------------

Looks good.

> Refactor creating and managing of Page Memory Indexes 
> ------------------------------------------------------
>
>                 Key: IGNITE-21742
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21742
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksandr Polovtcev
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Current logic of managing Page Memory indexes (like recovery, creation of new indexes and updates during rebalance) is all contained within the {{AbstractPageMemoryMvPartitionStorage}} which makes it complicated to modify it (like, for example when implementing recovery in IGNITE-21671). Also, current approach of creating or restoring Index Trees is not very convenient as it relies on a boolean flag passed to the corresponding constructor. It would be more readable and maintainable to have distinct factory methods for that. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)