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

Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2023/09/27 12:45:00 UTC

[jira] [Created] (IGNITE-20505) Preparing to implement IndexBuildController

Kirill Tkalenko created IGNITE-20505:
----------------------------------------

             Summary: 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
             Fix For: 3.0.0-beta2


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 IGNTIE-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)