[IGNITE-12715] Calcite integration. Secondary indexes support.

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: sql
• Assignee: Roman Kondakov
• Reporter: Roman Kondakov
• Created: 21/Feb/20 14:56
• Updated: 03/Nov/20 15:26
• Resolved: 27/May/20 13:41

Description

Secondary indexes should be supported by Calcite-based engine as well as they supported by the legacy H2 engine. At first we can use the old engine for indexes maintenance (building, updating, etc). In this case Calcite engine will only use indexes metadata for query planning and index scans for query execution. On the next iteration we need to eliminate the old engine usage.

Approximate plan for indexes support implementation:

1. Add indexes to schema and set up all schema listeners.
2. Add Collation to planner's output trait set and check if generated plan is properly chosen in accordance to index sort direction.
3. Implement index scans with filtering
4. Add Sort node to exec. 

 

Issue Links

• fixes: IGNITE-13026 Calcite integration. Fix metadata for IgniteTable when it has embedded filters.
• is part of: IGNITE-12248 Apache Calcite based query execution engine
• links to: GitHub Pull Request #7813