[
https://issues.apache.org/jira/browse/IGNITE-15096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428762#comment-17428762
]
Andrey Mashenkov commented on IGNITE-15096:
-------------------------------------------
Table registered too late.
Actually, events happen in the next order
* listener.onCreate is called for table configuration and run asynchronous
table initialization
* listener.onCreate is called for schema, but a table is required to register a
schema for the table. So, ends up with NPE.
* async operation register a table (put into a map).
Another issue is an initial schema is passed to the table constructor directly,
and the schema listener registers the same schema,
that cause duplicate 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)
