You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2023/02/03 09:51:00 UTC

[jira] [Updated] (IGNITE-13022) Calcite integration. Merge index conditions for the same field.

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

Evgeny Stanilovsky updated IGNITE-13022:
----------------------------------------
    Labels: calcite  (was: calcite calcite3-required)

> Calcite integration. Merge index conditions for the same field.
> ---------------------------------------------------------------
>
>                 Key: IGNITE-13022
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13022
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Roman Kondakov
>            Assignee: Aleksey Plekhanov
>            Priority: Minor
>              Labels: calcite
>             Fix For: 2.15
>
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> Index scans should be able to merge index conditions. For example query
> {code:java}
> SELECT * FROM tbl WHERE a<5 AND a<10
> {code}
> should be reduced to
>  
> {code:java}
> SELECT * FROM tbl WHERE a<5
> {code}
> Parameters should be handled in a more tricky way:
> {code:java}
> SELECT * FROM tbl WHERE a<?1 AND a<?2
> {code}
> can be rewritten as
> {code:java}
> SELECT * FROM tbl WHERE a<MIN(?1, ?2){code}
> where the expression {{MIN(?1, ?2)}} should be evaluated right before the execution when parameters are known.
>  
>  



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