[
https://issues.apache.org/jira/browse/IGNITE-18536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755936#comment-17755936
]
Andrey Mashenkov commented on IGNITE-18536:
-------------------------------------------
I mean when user do
{code:java}
ignite.tables().table("myTable")
{code}
there is no transaction yet, and we should use some "latest" metadata.
The alternatives are
* add Transaction to a method signature (please no)
* add a facade to any table name, then fail a table operation if a transaction
will not fount a table, that also looks shitty.
> 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)
