[
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-15424:
---------------------------------------
Description:
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.
was:
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.
> 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 implementation to
> the core module.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
