[IGNITE-16111] Calcite engine. Fallback to table scan if index is absent on some nodes

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: calcite
• Assignee: Aleksey Plekhanov
• Reporter: Aleksey Plekhanov
• Created: 13/Dec/21 15:16
• Updated: 22/Mar/22 15:14
• Resolved: 15/Feb/22 07:09

Description

Calcite-based SQL engine creates a plan on node initiator and uses only local node data for planning. The local node doesn't know about other nodes' indexes state, indexes on some nodes can be rebuilt during query execution, and fragments of the plan containing rebuilding indexes can't be executed on these nodes. In this case, we should provide some type of fallback. For example, if the status of the index is invalid and the plan contains an index scan, we should replace this index scan with the chain: sorted index spool -> sort -> table scan.
As a target solution, perhaps we should maintain global indexes state and make plans using this information

Issue Links

• blocks: IGNITE-15436 Calcite engine. Merge Calcite SQL Engine to Ignite 2.x
• is duplicated by: IGNITE-13035 Calcite integration. Support fallback on indexes rebuild
• is part of: IGNITE-12248 Apache Calcite based query execution engine
• relates to: IGNITE-16507 Calcite engine. Redundant sort node when rewriting index scan on index rebuild
• links to: GitHub Pull Request #9671