[IGNITE-20505] Preparing to implement IndexBuildController

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Labels: ignite-3
• Epic Link: Dynamic indexes creation
• Assignee: Kirill Tkalenko
• Reporter: Kirill Tkalenko
• Reviewer: Roman Puchkovskiy
• Created: 27/Sep/23 12:44
• Updated: 04/Sep/24 16:09
• Resolved: 28/Sep/23 12:11

Description

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.

Issue Links

• blocks: IGNITE-20330 Create an abstraction for building indexes
• is blocked by: IGNITE-20339 Get rid of IndexEvent and TableEvent
• links to: GitHub Pull Request #2638