[
https://issues.apache.org/jira/browse/IGNITE-16377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498788#comment-17498788
]
Vladislav Pyatkov commented on IGNITE-16377:
--------------------------------------------
This patch was merged to feature branch:
[ignite-16391|https://github.com/gridgain/apache-ignite-3/tree/ignite-16391].
> Notification listeners of TableManager should rely on causality tokens when
> referring to dependee components
> ------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-16377
> URL: https://issues.apache.org/jira/browse/IGNITE-16377
> Project: Ignite
> Issue Type: Improvement
> Reporter: Denis Chudov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> While handling the notifications, listeners should rely on the fact that the
> components that they depend on, won’t return stale or inconsistent data. It
> should be guaranteed by causality tokens mechanism.
> Listeners of TableManager should rely on the causality token futures to
> finish all the logic that depends on other components or other listeners.
> Therefore, this logic should be implemented in thenCompose blocks of
> causality futures.
> The listeners should be aware of the current state of the component and do
> every action in order to change the current state to the state that the
> component should have after applying the metastorage update.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
