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

Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2023/05/16 16:38:00 UTC

[jira] [Updated] (IGNITE-18537) Implement missed create/alter/drop Catalog operations

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

Andrey Mashenkov updated IGNITE-18537:
--------------------------------------
    Summary: Implement missed create/alter/drop Catalog operations  (was: Integrate versioned schema definitions into create/alter/drop operations)

> Implement missed create/alter/drop Catalog operations
> -----------------------------------------------------
>
>                 Key: IGNITE-18537
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18537
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Bessonov
>            Priority: Major
>              Labels: ignite-3
>
> Every CRETE/ALTER/DROP operation should lead to a new schema definition.
> Most likely, this must be the golden source of truth, instead of configuration.
> Please keep in mind that the affinity is not the part of the schema definition. Data storage parameters are not the part of it as well.
> TBD



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