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 2026/01/29 12:12:00 UTC
[jira] [Updated] (IGNITE-27700) Test TpchScale100Test.test[queryId=20] is flaky
[ https://issues.apache.org/jira/browse/IGNITE-27700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-27700:
---------------------------------------
Description:
Test TpchScale100Test.test[queryId=20] is flaky. For some reason plans are differnt between execution. But main problem: filter is not merged into scan.
See next plan part after {{trimUnusedFields}}:
{noformat}
LogicalProject(L_QUANTITY=[$2])
LogicalFilter(condition=[AND(=($0, $cor0.PS_PARTKEY), =($1, $cor0.PS_SUPPKEY), >=($3, 1994-01-01), <($3, +(1994-01-01, *(12:INTERVAL YEAR, 1))))])
LogicalProject(L_PARTKEY=[$3], L_SUPPKEY=[$4], L_QUANTITY=[$6], L_SHIPDATE=[$12])
IgniteLogicalTableScan(table=[[PUBLIC, LINEITEM]])
{noformat}
Filter can't transpose project ({{CoreRules.FILTER_PROJECT_TRANSPOSE}}), since it contains correlates. And part of filter condition can't be merged into scan ({{FilterScanMergeRule.TABLE_SCAN_SKIP_CORRELATED}}), since project node located between filter and scan.
Plans difference should be investigated separately.
was:
Test TpchScale100Test.test[queryId=20] is flaky. For some reason plans are differnt between execution. But main problem: filter is not merged into scan.
See next plan part after {{trimUnusedFields}}:
{noformat}
LogicalProject(L_QUANTITY=[$2])
LogicalFilter(condition=[AND(=($0, $cor0.PS_PARTKEY), =($1, $cor0.PS_SUPPKEY), >=($3, 1994-01-01), <($3, +(1994-01-01, *(12:INTERVAL YEAR, 1))))])
LogicalProject(L_PARTKEY=[$3], L_SUPPKEY=[$4], L_QUANTITY=[$6], L_SHIPDATE=[$12])
IgniteLogicalTableScan(table=[[PUBLIC, LINEITEM]])
{noformat}
Filter can't transpose project ({{CoreRules.FILTER_PROJECT_TRANSPOSE}}), since it contains correlates. And part of filter condition can't be merged into scan ({{FilterScanMergeRule.TABLE_SCAN_SKIP_CORRELATED}}), since project node located between filter and scan.
Plans difference should be investigated separately.
> Test TpchScale100Test.test[queryId=20] is flaky
> -----------------------------------------------
>
> Key: IGNITE-27700
> URL: https://issues.apache.org/jira/browse/IGNITE-27700
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: calcite, ise
>
> Test TpchScale100Test.test[queryId=20] is flaky. For some reason plans are differnt between execution. But main problem: filter is not merged into scan.
> See next plan part after {{trimUnusedFields}}:
> {noformat}
> LogicalProject(L_QUANTITY=[$2])
> LogicalFilter(condition=[AND(=($0, $cor0.PS_PARTKEY), =($1, $cor0.PS_SUPPKEY), >=($3, 1994-01-01), <($3, +(1994-01-01, *(12:INTERVAL YEAR, 1))))])
> LogicalProject(L_PARTKEY=[$3], L_SUPPKEY=[$4], L_QUANTITY=[$6], L_SHIPDATE=[$12])
> IgniteLogicalTableScan(table=[[PUBLIC, LINEITEM]])
> {noformat}
> Filter can't transpose project ({{CoreRules.FILTER_PROJECT_TRANSPOSE}}), since it contains correlates. And part of filter condition can't be merged into scan ({{FilterScanMergeRule.TABLE_SCAN_SKIP_CORRELATED}}), since project node located between filter and scan.
> Plans difference should be investigated separately.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)