[
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597725#comment-17597725
]
Taras Ledkov edited comment on IGNITE-15424 at 8/30/22 9:46 AM:
----------------------------------------------------------------
[~alex_pl], please take a look at the comment in the PR.
The patch is OK with me.
Please fix synchronization for the {{H2SchemaManager}} and {{SchemaManager}}.
was (Author: tledkov):
[~alex_pl], please take a look at the comment in the PR.
The patch is OK with me.
Please fix synchronization for the `H2SchemaManager` and `SchemaManager`.
> 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: calcite2-required, ignite-osgi, important, osgi
> Fix For: 2.14
>
> Time Spent: 1h 20m
> 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)
