[
https://issues.apache.org/jira/browse/IGNITE-21742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-21742:
-----------------------------------------
Description: 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.
> Refactor creating and managing 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
> Time Spent: 10m
> 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)
