[
https://issues.apache.org/jira/browse/IGNITE-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-19209:
---------------------------------------
Description:
At the moment there is a CatalogService that manages SchemaDescriptors
(database schemas, not table schemas) and TableDescriptors. CREATE TABLE is
being handled by the CatalogService, however it seems like it doesn't actually
write the schema to the metastorage.
I believe that the following must be done in the scope of this ticket:
# Actually write new schema to the metastorage.
# Use node's HLC + DD (Delay Duration) which is described in the
[https://cwiki.apache.org/confluence/display/IGNITE/IEP-98%3A+Schema+Synchronization]
as the new schema's activation time.
# Complete the user's 'initiate a schema update' at the activation time + max
clock skew
was:
At the moment there is a CatalogService that manages SchemaDescriptors
(database schemas, not table schemas) and TableDescriptors. CREATE TABLE is
being handled by the CatalogService, however it seems like it doesn't actually
write the schema to the metastorage.
I believe that two things must be done in the scope of this ticket:
1. Actually write new schema to the metastorage.
2. Use node's HLC + DD (Delay Duration) which is described in the
https://cwiki.apache.org/confluence/display/IGNITE/IEP-98%3A+Schema+Synchronization
as the new schema's activation time.
> Implement installing table schema updates
> -----------------------------------------
>
> Key: IGNITE-19209
> URL: https://issues.apache.org/jira/browse/IGNITE-19209
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> At the moment there is a CatalogService that manages SchemaDescriptors
> (database schemas, not table schemas) and TableDescriptors. CREATE TABLE is
> being handled by the CatalogService, however it seems like it doesn't
> actually write the schema to the metastorage.
> I believe that the following must be done in the scope of this ticket:
> # Actually write new schema to the metastorage.
> # Use node's HLC + DD (Delay Duration) which is described in the
> [https://cwiki.apache.org/confluence/display/IGNITE/IEP-98%3A+Schema+Synchronization]
> as the new schema's activation time.
> # Complete the user's 'initiate a schema update' at the activation time +
> max clock skew
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
