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

[Ignite TC Bot (Jira)]

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

Ignite TC Bot commented on IGNITE-13022:


{panel:title=Branch: [pull/10306/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility 2{color} [[tests 
1|https://ci2.ignite.apache.org/viewLog.html?buildId=6816459]]
* IgniteControlUtilityTestSuite2: 
GridCommandHandlerDefragmentationTest.testDefragmentationStatus - History for 
base branch is absent.

{panel}
{panel:title=Branch: [pull/10306/head] Base: [master] : New Tests 
(13)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Calcite SQL{color} [[tests 
13|https://ci2.ignite.apache.org/viewLog.html?buildId=6813457]]
* {color:#013220}IgniteCalciteTestSuite: 
IndexSearchBoundsPlannerTest.testBoundsMerge - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: 
IndexSearchBoundsPlannerTest.testBoundsOneFieldSearchRangeOptimization - 
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: 
IndexSearchBoundsPlannerTest.testBoundsSeveralFieldsSearch - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: 
IndexSearchBoundsPlannerTest.testBoundsMaxComplexity - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: 
IndexSearchBoundsPlannerTest.testBoundsOneFieldSearchWithNull - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: 
IndexSearchBoundsPlannerTest.testBoundsOneFieldSearchDeduplication - 
PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: 
IndexSearchBoundsPlannerTest.testBoundsOneFieldSearch - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: 
IndexSearchBoundsPlannerTest.testBoundsDescOrdering - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: 
IndexSearchBoundsPlannerTest.testBoundsWithCorrelate - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: 
CalciteBasicSecondaryIndexIntegrationTest.testIndexBoundsMerge - PASSED{color}
* {color:#013220}IgniteCalciteTestSuite: 
IndexSearchBoundsPlannerTest.testBoundsTypeConversion - PASSED{color}
... and 2 new tests

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6813537buildTypeId=IgniteTests24Java8_RunAll]

> 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: calcite2-required, calcite3-required
>  Time Spent: 10m
>  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 {code}
> can be rewritten as
> {code:java}
> SELECT * FROM tbl WHERE a 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)

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

[Roman Kondakov (Jira)]

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

Roman Kondakov commented on IGNITE-13022:
-

We also need to check that it works for  {{BETWEEN}} clause.  As well as it 
works in the presence of filters over several tables.

> 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
>Priority: Major
>
> 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 {code}
> can be rewritten as
> {code:java}
> SELECT * FROM tbl WHERE a 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.3.4#803005)