You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2022/09/29 10:36:00 UTC
[jira] [Assigned] (IGNITE-17702) Move schema changes history from configuration to metastore
[ https://issues.apache.org/jira/browse/IGNITE-17702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgeny Stanilovsky reassigned IGNITE-17702:
-------------------------------------------
Assignee: Evgeny Stanilovsky
> Move schema changes history from configuration to metastore
> -----------------------------------------------------------
>
> Key: IGNITE-17702
> URL: https://issues.apache.org/jira/browse/IGNITE-17702
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Evgeny Stanilovsky
> Priority: Major
> Labels: ignite-3, tech-debt
>
> History of schema changes keeps in configuration.Looks like it wrong, due to configuration it is just a thing which requires to recreate similar cluster. History schema more looks like a internal part which could keeps in Metastore.
> Start points:
> org.apache.ignite.internal.configuration.schema.SchemaConfigurationSchema
> org.apache.ignite.internal.configuration.schema.ExtendedTableConfigurationSchema
--
This message was sent by Atlassian Jira
(v8.20.10#820010)