[
https://issues.apache.org/jira/browse/IGNITE-18537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-18537:
--------------------------------------
Description:
Every CRETE/ALTER/DROP operation should trigger a new Catalog version.
We already have CREATE TABLE DDL operation implemented. Let's implement others
in similar way.
Please keep in mind that Distribution zones is out of scope now. -the affinity
is not the part of the schema definition. Data storage parameters are not the
part of it as well.-
was:
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
> 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 trigger a new Catalog version.
> We already have CREATE TABLE DDL operation implemented. Let's implement
> others in similar way.
> Please keep in mind that Distribution zones is out of scope now. -the
> affinity is not the part of the schema definition. Data storage parameters
> are not the part of it as well.-
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
