[
https://issues.apache.org/jira/browse/IGNITE-20638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783122#comment-17783122
]
Roman Puchkovskiy commented on IGNITE-20638:
--------------------------------------------
The patch looks good to me
> Integration of distributed index building
> -----------------------------------------
>
> Key: IGNITE-20638
> URL: https://issues.apache.org/jira/browse/IGNITE-20638
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> We need to integrate
> *org.apache.ignite.internal.index.IndexAvailabilityController* into
> *org.apache.ignite.internal.app.IgniteImpl*.
> But there are nuances that I would like to solve in the current ticket:
> * We have created several components around the index building mechanism that
> would be convenient to keep in one place; I suggest creating the
> *IndexBuildingManager*. Which will contain all the components we need to work
> with building the index.
> * *org.apache.ignite.internal.index.IndexBuildController* - should not be a
> *IgniteComponent* and should not close *IndexBuilder* as it will be used by
> two components.
> * *org.apache.ignite.internal.table.distributed.index.IndexBuilder* and
> related classes are moved to module *ignite-index*.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)