[jira] [Commented] (IGNITE-19209) Implement installing table schema updates

["Roman Puchkovskiy (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726637#comment-17726637 ] 

Roman Puchkovskiy commented on IGNITE-19209:
--------------------------------------------

Item 1 (writing schema updates to the Metastorage and having indices by timestamp and version) are already implemented, so we only need to make sure that activation time is computed in accordance with the Schema Sync IEP. To do so, we might need to embed activation time calculation in the CatalogManager, or we might pass in a closure that would do the calculation. This is needed because CatalogManager uses a CAS loop to write updates, so activation time has to be recalculated on each iteration of the CAS loop.

> 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
>            Priority: Major
>              Labels: ignite-3
>
> 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. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)