[
https://issues.apache.org/jira/browse/IGNITE-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482284#comment-17482284
]
Evgeny Stanilovsky edited comment on IGNITE-16046 at 1/26/22, 6:42 AM:
-----------------------------------------------------------------------
seems we need to investigate improvements from [1] and usage of
CoreRules#JOIN_TO_MULTI_JOIN -> CoreRules#MULTI_JOIN_OPTIMIZE
[1] https://issues.apache.org/jira/browse/CALCITE-4515
was (Author: zstan):
seems we need to investigate improvements from [1] and usage of
CoreRules#MULTI_JOIN_OPTIMIZE
[1] https://issues.apache.org/jira/browse/CALCITE-4515
> Calcite engine. Double JOIN hangs on optimization phase
> -------------------------------------------------------
>
> Key: IGNITE-16046
> URL: https://issues.apache.org/jira/browse/IGNITE-16046
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Ivan Daschinsky
> Priority: Major
> Labels: calcite2-required, calcite3-required, ignite-3
> Attachments: IGNITE-16046_Combinatorial_explosions.patch
>
>
> Reproducer:
> {noformat}
> CREATE TABLE T1(A INT, B INT);
> CREATE TABLE T2(A INT, C INT);
> CREATE TABLE T3(B INT, C INT);
> SELECT * FROM T1 JOIN T2 ON (T1.A = T2.A) JOIN T3 ON (T1.B = T3.B AND T2.C =
> T3.C);
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
