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

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.14
• Labels: calcite important
• 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
• Ignite Flags: Release Notes Required
• Assignee: Aleksey Plekhanov
• Reporter: Aleksey Plekhanov
• Created: 24/Jun/22 07:29
• Updated: 03/Oct/22 11:04
• Resolved: 01/Sep/22 07:28

Description

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. 

Issue Links

• incorporates: IGNITE-15424 Calcite engine. Move schema management infrastructure to the core module
• incorporates: IGNITE-16977 Move DATE/TIME/TIMESTAMP indexes processing from ignite-indexing module to core
• incorporates: IGNITE-17046 Move H2RowComparator logic to the core module
• incorporates: IGNITE-17190 Calcite engine. Unbind statistics from H2
• incorporates: IGNITE-17227 Move RunningQueryManager to the core module
• incorporates: IGNITE-17344 Move "metrics" SQL system view to GridSystemViewManager
• incorporates: IGNITE-17364 Move control utility index tasks to the core module
• is part of: IGNITE-12248 Apache Calcite based query execution engine
• is related to: IGNITE-17800 Make ODBC query handler independent from H2 indexing.
• relates to: IGNITE-17598 Unbind some JDBC/ODBC metadata requests from the ignite-indexing module
• relates to: IGNITE-17599 Calcite engine. Support LocalDate/LocalTime types