You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2023/05/16 16:34:00 UTC

[jira] [Commented] (IGNITE-18536) Versioned schema definitions synchronization

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

Andrey Mashenkov commented on IGNITE-18536:
-------------------------------------------

I'd suggest to rewrite description in terms of Catalog and Schema synchronization.
Smth like, we should wait for DD time before getting new catalog version allowed for using, and we should rely on Schema synchonization components when resolve Tx begin timestamp to latest Catalog version that is visible for the Tx.

> Versioned schema definitions synchronization
> --------------------------------------------
>
>                 Key: IGNITE-18536
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18536
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Bessonov
>            Priority: Major
>              Labels: ignite-3
>
> TBD.
> Metadata synchronization should be used, implemented (most likely) on top of "transactions in the past", defined in the transactions IEP (see "Lock-free RW Transactions" in https://cwiki.apache.org/confluence/display/IGNITE/IEP-91:+Transaction+protocol).



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