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

[Ignite TC Bot (Jira)]

    [ 
https://issues.apache.org/jira/browse/IGNITE-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17585459#comment-17585459
 ] 

Ignite TC Bot commented on IGNITE-15424:
----------------------------------------

{panel:title=Branch: [pull/10200/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10200/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6749423&buildTypeId=IgniteTests24Java8_RunAll]

> 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: 10m
>  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)