[
https://issues.apache.org/jira/browse/IGNITE-18536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756000#comment-17756000
]
Roman Puchkovskiy commented on IGNITE-18536:
--------------------------------------------
Make do schema sync, we don't need a transaction, a timestamp is enough. For
the APIs where a timestamp is not available (like in the example of
table("name")), the implementation should take ts=HLC.now() and then await for
the schemas to be complete wrt this timestamp before proceeding.
> Schema synchronization feature and Catalog feature integration
> --------------------------------------------------------------
>
> Key: IGNITE-18536
> URL: https://issues.apache.org/jira/browse/IGNITE-18536
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Priority: Blocker
> Labels: ignite-3
>
> 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).
> Let's plug SchemaSychronizationManager into Ignite node and use it for
> waiting actual metadata before resolve actual Catalog version for a
> transaction.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
