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

Vladislav Pyatkov commented on IGNITE-16550:
--------------------------------------------

[~Denis Chudov] I left a few comments in the PR. Please look at them.

> Redesign SchemaRegistry to use causality tokens
> -----------------------------------------------
>
>                 Key: IGNITE-16550
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16550
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Assignee: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> SchemaRegistry designed before the causality logic aspired(IGNITE-16391), by 
> the reason all method do not apply a token and work synchronously.
> After the redesign part of the methods should be removed 
> (SchemaRegistry#lastSchemaVersion, SchemaRegistry#waitLatestSchema), others 
> should entirely depend on causality.
> Possibly the new methods will return futures.
> UPD:
> It was decided that in the current ticket it's worth to decouple Schema logic 
> from the {{TableManager}} and create a new manager called {{SchemaManager}}, 
> so we can integrate causality tokens logic to the {{SchemaManager}}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to