[
https://issues.apache.org/jira/browse/IGNITE-13151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147600#comment-17147600
]
Sergey Chugunov commented on IGNITE-13151:
------------------------------------------
[~akalashnikov],
As far as I understand, this patch just moves checkpointer code and related
interfaces outside of GridCacheDatabaseSharedManager class, no structural
refactoring was made.
>From that perspective change looks good to me.
How do you estimate risks of merging it to master before upcoming 2.9 release?
> Checkpointer code refactoring: extracting classes from
> GridCacheDatabaseSharedManager
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-13151
> URL: https://issues.apache.org/jira/browse/IGNITE-13151
> Project: Ignite
> Issue Type: Sub-task
> Components: persistence
> Reporter: Sergey Chugunov
> Assignee: Anton Kalashnikov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Checkpointer is at the center of Ignite persistence subsystem and more people
> from the community understand it the better means it is more stable and more
> efficient.
> However for now checkpointer code sits inside of
> GridCacheDatabaseSharedManager class and is entangled with this higher-level
> and more general component.
> To take a step forward to more modular checkpointer we need to do two things:
> # Move checkpointer code outside database manager to a separate class.
> (That's what this ticket is about.)
> # Create a well-defined API of checkpointer that will allow us to create new
> implementations of checkpointer in the future. An example of this is new
> checkpointer implementation needed for defragmentation feature purposes.
> (Should be done in a separate ticket)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
