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

Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2025/01/23 12:00:00 UTC

[jira] [Assigned] (IGNITE-24247) Catalog. Indexes created with table must be created in AVAILABLE state

     [ https://issues.apache.org/jira/browse/IGNITE-24247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Pereslegin reassigned IGNITE-24247:
-----------------------------------------

    Assignee: Pavel Pereslegin

> Catalog. Indexes created with table must be created in AVAILABLE state
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-24247
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24247
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Assignee: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> Currently, every catalog command from a batch is processed as it was run in alone. Given the complex lifecycle of indexes, this can be improved by creating secondary indexes in AVAILABLE state as it is done for primary key index. The only condition is such indexes must be created in the same batch in which table referenced by indexes is created.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)