[
https://issues.apache.org/jira/browse/IGNITE-18536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755931#comment-17755931
]
Andrey Mashenkov commented on IGNITE-18536:
-------------------------------------------
[~rpuch], you refers IGNITE-19226, which is about awaiting for actual schema
for table operaion, and looks like a dulipcate.
I've fixed a description to the ticket, this one is about waiting for actual
schema for SQL queries.
The main difference is in SQL we have a transaction and wait for actual schema
for it; in TableManager we get a table first;
When getting a table, we expect we have a latest metadata to see recently
created table, regardless we already have some transaction or not.
Further, a table operation will got/start a transaction and will wait table
schema as SQL do.
> 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)
