You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ivan Daschinsky (Jira)" <ji...@apache.org> on 2022/04/08 13:24:00 UTC

[jira] [Assigned] (IGNITE-15424) Calcite engine. Move schema management infrastructure to the core module

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

Ivan Daschinsky reassigned IGNITE-15424:
----------------------------------------

    Assignee: Ivan Daschinsky

> Calcite engine. Move schema management infrastructure to the core module 
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-15424
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15424
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksey Plekhanov
>            Assignee: Ivan Daschinsky
>            Priority: Major
>              Labels: calcite2-required, calcite3-required
>
> Currently, schema management commands initiated in the {{ignite-core}} module, but all processing implemented in the {{ignite-indexing}} module. Ignite Calciite SQL engine use {{SchemaChangeListener}} to maintain own structures. 
> To get rid of {{ignite-indexing}} (and H2) dependency from the {{ignite-calcite}} module we should move schema management and statistics management implementation to the core module.



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