[jira] [Created] (IGNITE-16920) The performance of the COUNT function in the Calcite based SQL Engine is significantly lower than that in the H2 based SQL Engine

2022-04-30 Thread YuJue Li (Jira) 
YuJue Li created IGNITE-16920:
-

 Summary: The performance of the COUNT function in the Calcite 
based SQL Engine is significantly lower than that in the H2 based SQL Engine
 Key: IGNITE-16920
 URL: https://issues.apache.org/jira/browse/IGNITE-16920
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Affects Versions: 2.13
Reporter: YuJue Li
 Fix For: 2.14
 Attachments: PI_COM_DAY.sql, example-calcite.xml, 
image-2022-05-01-13-35-59-275.png

!image-2022-05-01-13-35-59-275.png!



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Updated] (IGNITE-16919) H2 Index cost function must take into account only corresponding columns.

2022-04-30 Thread Evgeny Stanilovsky (Jira) 


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

Evgeny Stanilovsky updated IGNITE-16919:

Summary: H2 Index cost function must take into account only corresponding 
columns.  (was: Index cost function must take into account only corresponding 
columns.)

> H2 Index cost function must take into account only corresponding columns.
> -
>
> Key: IGNITE-16919
> URL: https://issues.apache.org/jira/browse/IGNITE-16919
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.13
>Reporter: Evgeny Stanilovsky
>Assignee: Evgeny Stanilovsky
>Priority: Major
> Attachments: image-2022-04-30-19-13-59-997.png
>
>
> H2IndexCostedBase#getCostRangeIndex is called with allColumnsSet where 
> consists columns from all operating tables, check: 
> org.h2.table.Plan#calculateCost :
> {code:java}
> final HashSet allColumnsSet = ExpressionVisitor
> .allColumnsForTableFilters(allFilters);
> {code}
> thus allColumnsSet consist columns from all operating tables
>  !image-2022-04-30-19-13-59-997.png! 
> and erroneous iteration here:
> H2IndexCostedBase#getCostRangeIndex
> ...
> {code:java}
> if (!isScanIndex && allColumnsSet != null && !skipColumnsIntersection && 
> !allColumnsSet.isEmpty()) {
> boolean foundAllColumnsWeNeed = true;
> for (Column c : allColumnsSet) { // <-- all columns
> {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Created] (IGNITE-16919) Index cost function must take into account only corresponding columns.

2022-04-30 Thread Evgeny Stanilovsky (Jira) 
Evgeny Stanilovsky created IGNITE-16919:
---

 Summary: Index cost function must take into account only 
corresponding columns.
 Key: IGNITE-16919
 URL: https://issues.apache.org/jira/browse/IGNITE-16919
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.13
Reporter: Evgeny Stanilovsky
Assignee: Evgeny Stanilovsky
 Attachments: image-2022-04-30-19-13-59-997.png

H2IndexCostedBase#getCostRangeIndex is called with allColumnsSet where consists 
columns from all operating tables, check: 
org.h2.table.Plan#calculateCost :

{code:java}
final HashSet allColumnsSet = ExpressionVisitor
.allColumnsForTableFilters(allFilters);
{code}

thus allColumnsSet consist columns from all operating tables
 !image-2022-04-30-19-13-59-997.png! 
and erroneous iteration here:
H2IndexCostedBase#getCostRangeIndex
...

{code:java}
if (!isScanIndex && allColumnsSet != null && !skipColumnsIntersection && 
!allColumnsSet.isEmpty()) {
boolean foundAllColumnsWeNeed = true;

for (Column c : allColumnsSet) { // <-- all columns
{code}




--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Commented] (IGNITE-16904) Release Apache Ignite 2.13

2022-04-30 Thread Amelchev Nikita (Jira) 


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

Amelchev Nikita commented on IGNITE-16904:
--

[~nsafonov], Thank you!

> Release Apache Ignite 2.13
> --
>
> Key: IGNITE-16904
> URL: https://issues.apache.org/jira/browse/IGNITE-16904
> Project: Ignite
>  Issue Type: Task
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Commented] (IGNITE-16917) Fix deploy configuration for the ignite-calcite module

2022-04-30 Thread Ignite TC Bot (Jira) 


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

Ignite TC Bot commented on IGNITE-16917:


{panel:title=Branch: [pull/10006/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10006/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6413641buildTypeId=IgniteTests24Java8_RunAll]

> Fix deploy configuration for the ignite-calcite module
> --
>
> Key: IGNITE-16917
> URL: https://issues.apache.org/jira/browse/IGNITE-16917
> Project: Ignite
>  Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.14
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The ignite-calcite module should not skip deploy.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)