[
https://issues.apache.org/jira/browse/IGNITE-17766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy resolved IGNITE-17766.
----------------------------------------
Fix Version/s: 3.0
Resolution: Fixed
> Ignite 3.0: Dynamically created SQL indexes lifecycle and management, basic
> cases
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-17766
> URL: https://issues.apache.org/jira/browse/IGNITE-17766
> Project: Ignite
> Issue Type: Epic
> Components: persistence
> Reporter: Sergey Chugunov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
>
> Executing dynamic index management with CREATE/DROP INDEX commands requires
> specific management of index lifecycle.
> It includes at least:
> # Triggering necessary operation on affinity nodes (nodes hosting data of a
> table with new index).
> # Adding information about new index to configuration.
> # Monitoring process of index creation and updating index status.
> # Providing notification mechanism to SQL engine so index will be used if and
> only if it is fully built and ready to be used.
> # Cancelling operation and cleaning stuff up in case user drops index.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
