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

["Konstantin Orlov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-16111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483210#comment-17483210 ] 

Konstantin Orlov commented on IGNITE-16111:
-------------------------------------------

Hi [~alex_pl]! I'm generally ok with provided changes. Left a few comments though

> 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: calcite2-required, calcite3-required
>          Time Spent: 1h 40m
>  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)