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

Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2022/09/01 07:22:00 UTC

[jira] [Updated] (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 ]

Aleksey Plekhanov updated IGNITE-15424:
---------------------------------------
    Labels: ignite-osgi important osgi  (was: calcite2-required ignite-osgi important osgi)

> 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: Aleksey Plekhanov
>            Priority: Major
>              Labels: ignite-osgi, important, osgi
>             Fix For: 2.14
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> 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 implementation to the core module.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)