You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2021/11/17 09:25:00 UTC

[jira] [Resolved] (IGNITE-15096) Schema events processing refactoring.

     [ https://issues.apache.org/jira/browse/IGNITE-15096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yury Gerzhedovich resolved IGNITE-15096.
----------------------------------------
    Resolution: Invalid

not an actual

> 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
> Update:
> Now we register a per-table listener for schema changes + listener for partition affinity assignment.
> A single listener for schema changes and single listener for affinity changes will be enough,
> but table registration may be tricky a bit.
> Let's discuss and fix this.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)