[
https://issues.apache.org/jira/browse/IGNITE-16111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-16111:
---------------------------------------
Labels: calcite calcite3-required (was: calcite2-required
calcite3-required)
> Calcite engine. Fallback to table scan if index is absent on some nodes
> -----------------------------------------------------------------------
>
> Key: IGNITE-16111
> URL: https://issues.apache.org/jira/browse/IGNITE-16111
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: calcite, calcite3-required
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
