[
https://issues.apache.org/jira/browse/IGNITE-18536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723190#comment-17723190
]
Andrey Mashenkov edited comment on IGNITE-18536 at 5/16/23 4:33 PM:
--------------------------------------------------------------------
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.
Or I didn't catch what is the ticket about?
was (Author: amashenkov):
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)
