[ 
https://issues.apache.org/jira/browse/IGNITE-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yury Gerzhedovich updated IGNITE-13568:
---------------------------------------
    Epic Link: IGNITE-19479

> Calcite integration. Decrease bounds of index scan
> --------------------------------------------------
>
>                 Key: IGNITE-13568
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13568
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Yury Gerzhedovich
>            Priority: Minor
>              Labels: calcite2-required, calcite3-required
>
> As of now, we analyze just the first column from predicate to detemine lower 
> and upper bounds for complex indexes in case first predicate is not equal. It 
> decreasing search space, however for particular cases, it could be not so 
> effective, for example, the selectivity of the first column is very low. We 
> need to take into account all columns from predicate and suitable index. Need 
> to keep in mind that each column at the index could be sorted in a different 
> manner.
> Start point right now is 
> org.apache.ignite.internal.processors.query.calcite.util.RexUtils#buildIndexConditions,
>  could be refactored before the ticked will be started.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to