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

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/05/22 10:28:00 UTC

[jira] [Commented] (IGNITE-19396) Move work with indexes from StorageUpdateHandler to a separate class

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

Roman Puchkovskiy commented on IGNITE-19396:
--------------------------------------------

The patch looks good to me

> Move work with indexes from StorageUpdateHandler to a separate class
> --------------------------------------------------------------------
>
>                 Key: IGNITE-19396
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19396
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> For the garbage collector, *org.apache.ignite.internal.table.distributed.StorageUpdateHandler* is used because it performs work with indexes, which is not entirely correct, it is worth moving work with indexes from *StorageUpdateHandler* into a separate class.
> It would also be nice to do garbage collection in batches in *org.apache.ignite.internal.table.distributed.gc.MvGc*.



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