[
https://issues.apache.org/jira/browse/IGNITE-20505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770008#comment-17770008
]
Roman Puchkovskiy commented on IGNITE-20505:
--------------------------------------------
The patch looks good to me
> Preparing to implement IndexBuildController
> -------------------------------------------
>
> Key: IGNITE-20505
> URL: https://issues.apache.org/jira/browse/IGNITE-20505
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Since the first implementation of IGNITE-20330 was unsuccessful due to the
> components being too tightly coupled, it was decided that index building
> should become a separate component (*IndexBuildController*) that would listen
> to *IndexManager* and *PlacementDriver* events and start or stop index
> building. Since in IGNITE-20339 the *IndexEvent* will be deleted, and in
> general we don’t need them, we will use the *CatalogManager* to listen only
> to its events, but we will add method *IndexManager#mvTableStorage(long
> causalityToken, int tableId)* that will create *IndexStorage* for all
> partitions.
> It would just be also good to add *IndexBuilder#stopBuildIndexes(int
> indexId)* within this ticket to stop building indexes for all partitions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
