[jira] [Resolved] (IGNITE-17226) Calcite engine. Make calcite engine independent of H2 and ignite-indexing

["Aleksey Plekhanov (Jira)" <ji...@apache.org>]

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

Aleksey Plekhanov resolved IGNITE-17226.
----------------------------------------
    Release Note: Calcite-based SQL engine is now independent of H2-based SQL engine and doesn't require 'ignite-indexing' module and H2 to be in classpath anymore
      Resolution: Fixed

> Calcite engine. Make calcite engine independent of H2 and ignite-indexing
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-17226
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17226
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Aleksey Plekhanov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: calcite, important
>             Fix For: 2.14
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, some functionality from ignite-indexing is still required for Calcite-based SQL engine, we should move such a functionality to the core module to make Calcite-based SQL engine fully independent of H2 and the ignite-indexing module.
> This is an umbrella ticket for migrating parts of the ignite-indexing. 



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