You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/05/17 11:06:00 UTC
[jira] [Assigned] (IGNITE-19483) Transform TableManager and IndexManager to internally work against Catalog event types
[ https://issues.apache.org/jira/browse/IGNITE-19483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Puchkovskiy reassigned IGNITE-19483:
------------------------------------------
Assignee: Roman Puchkovskiy
> Transform TableManager and IndexManager to internally work against Catalog event types
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-19483
> URL: https://issues.apache.org/jira/browse/IGNITE-19483
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, when an event like 'table was added to configuration' happens, the listener pools the table config by itself and then uses it to create the table.
> This should be changed: the table configuration object should be converted to an object from Catalog domain and pushed to the listeners.
> Same should be done to indices.
> Requires investigation.
> Also, we need to stop passing configuration to deeply-nested components (like storages). Also requires investigation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)