[
https://issues.apache.org/jira/browse/IGNITE-19502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-19502:
-------------------------------------
Description:
Right now database schema information in Ignite 3.0 is stored and treated as
regular configuration. All business processes related to schema changes are
distributed via internal mechanisms of configuration engine and orchestrated
ad-hoc by consumer components like TableManager or IndexManager.
But there is a strong evidence that API and guarantees of configuration engine
don't satisfy important requirements that emerge in the field of db schema
management.
So we need to stop treating schema as any other configuration and move it to a
separate component called Catalog Service.
This component will provide high-level API to modify the schema and will take
responsibility for all other necessary processes like synchronizing schema
changes between nodes, managing schema change events, notifying all necessary
components and providing orchestration between them.
was:
Right now database schema information in Ignite 3.0 is stored and treated as
regular configuration. All business processes related to schema changes are
distributed via internal mechanisms of configuration engine and orchestrated
ad-hoc by consumer components like TableManager or IndexManager.
But there is a strong evidence that API and guarantees of configuration engine
don't satisfy important requirements that emerge in the field of db schema
management.
So we need to stop treating schema as any other configuration and move it to a
separate component called Catalog Service.
This component will provide high-level API to modify the schema and take
responsibility for all other necessary processes like synchronizing schema
changes between nodes, managing schema change events, notifying all necessary
components and providing orchestration between them.
> Separate component to keep database schema and manage changes in it
> -------------------------------------------------------------------
>
> Key: IGNITE-19502
> URL: https://issues.apache.org/jira/browse/IGNITE-19502
> Project: Ignite
> Issue Type: Epic
> Components: persistence, sql
> Reporter: Sergey Chugunov
> Priority: Major
> Labels: ignite-3
>
> Right now database schema information in Ignite 3.0 is stored and treated as
> regular configuration. All business processes related to schema changes are
> distributed via internal mechanisms of configuration engine and orchestrated
> ad-hoc by consumer components like TableManager or IndexManager.
> But there is a strong evidence that API and guarantees of configuration
> engine don't satisfy important requirements that emerge in the field of db
> schema management.
> So we need to stop treating schema as any other configuration and move it to
> a separate component called Catalog Service.
> This component will provide high-level API to modify the schema and will take
> responsibility for all other necessary processes like synchronizing schema
> changes between nodes, managing schema change events, notifying all necessary
> components and providing orchestration between them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
