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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.14
• Labels: ignite-osgi osgi
• Assignee: Aleksey Plekhanov
• Reporter: Aleksey Plekhanov
• Created: 02/Sep/21 09:26
• Updated: 31/Oct/22 15:29
• Resolved: 01/Sep/22 07:20

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.

Issue Links

• incorporates: IGNITE-16667 AFFINITY_COLUMN & PK column in the TABLE_COLUMNS view are always FALSE.
• is part of: IGNITE-12248 Apache Calcite based query execution engine
• is part of: IGNITE-17226 Calcite engine. Make calcite engine independent of H2 and ignite-indexing
• is related to: IGNITE-11368 use the same information about indexes for JDBC drivers as for system view INDEXES
• links to: GitHub Pull Request #174
• links to: GitHub Pull Request #10200
• links to: PR to ignite-extensions