[ https://issues.apache.org/jira/browse/IGNITE-14034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yury Gerzhedovich updated IGNITE-14034: --------------------------------------- Labels: calcite2-required calcite3-required (was: ) > 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 > Priority: Major > Labels: calcite2-required, calcite3-required > > 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.3.4#803005)