You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2022/09/26 10:47:00 UTC

[jira] [Resolved] (IGNITE-14034) Calcite integration. IndexCondition refactoring

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

Aleksey Plekhanov resolved IGNITE-14034.
----------------------------------------
    Fix Version/s: 2.15
         Assignee: Aleksey Plekhanov
       Resolution: Fixed

Resolved IGNITE-15425

> Calcite integration. IndexCondition refactoring
> -----------------------------------------------
>
>                 Key: IGNITE-14034
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14034
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: calcite2-required, calcite3-required
>             Fix For: 2.15
>
>
> Currently IndexCondition is quite cumbersome and hard to understand. The difference between bounds and conditions is unclear as well as unclear what should be used to estimate a selectivity and what should be used to estimate a self cost.
> Thus I suggest to change it in a follow way:
>  * remove [lower|upper]Cond
>  * bounds remains as is
>  * self cost estimation of an AbstractIndex should be calculated with regard to bounds
>  * selectivity should be calculated with regards to whole condition that is member of ProjectableFilterableTableScan



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