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

Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2022/10/03 09:32:00 UTC

[jira] [Updated] (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 ]

Konstantin Orlov updated IGNITE-17702:
--------------------------------------
    Ignite Flags:   (was: Docs Required,Release Notes Required)

> 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
>             Fix For: 3.0.0-alpha6
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)