[IGNITE-16334] Calcite. Need to investigate why *Join*Rule ordering can affect the final plan.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: sql
• Labels: calcite calcite2-required ignite-3
• Assignee: Unassigned
• Reporter: Evgeny Stanilovsky
• Created: 19/Jan/22 13:45
• Updated: 18/Apr/24 05:47

Description

For now in optimization phase we have such join rules ordering, if MergeJoinConverterRule occurs at the end of this enumeration some tests will be failed.

                    MergeJoinConverterRule.INSTANCE,
                    CorrelatedNestedLoopJoinRule.INSTANCE,
                    CorrelateToNestedLoopRule.INSTANCE,
                    NestedLoopJoinConverterRule.INSTANCE,

Seems [1] can point out the root of such a problem.

[1] https://issues.apache.org/jira/browse/CALCITE-4542

Issue Links

• is part of: IGNITE-12248 Apache Calcite based query execution engine
• is related to: IGNITE-16333 Calcite. IgniteProject need to be initialized with single distribution.