[
https://issues.apache.org/jira/browse/IGNITE-15096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428763#comment-17428763
]
Andrey Mashenkov commented on IGNITE-15096:
-------------------------------------------
So, we have to
# introduce table initialization futures (or publish partially initialized
tables) to prevent early schema registration
# remove a schema from the constructor
# make "table created" event consistent with initial schema registration.
> Schema events processing refactoring.
> -------------------------------------
>
> Key: IGNITE-15096
> URL: https://issues.apache.org/jira/browse/IGNITE-15096
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Mashenkov
> Assignee: Andrey Mashenkov
> Priority: Minor
> Labels: ignite-3
> Time Spent: 40m
> Remaining Estimate: 0h
>
> All table events with schema events are processed in TableManager listener.
> Let's
> * -Replace ConfigurationListener with ConfigurationNamedListListener to
> simplify the diff calculation between old/new configs.-
> Resolved in IGNITE-15404
> * -Register a separate per-table listener for schema events on table creation.
> Resolved in IGNITE-15409
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
