[
https://issues.apache.org/jira/browse/IGNITE-16334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-16334:
----------------------------------------
Labels: calcite calcite2-required ignite-3 (was: calcite calcite2-required
calcite3-required)
> Calcite. Need to investigate why *Join*Rule ordering can affect the final
> plan.
> -------------------------------------------------------------------------------
>
> Key: IGNITE-16334
> URL: https://issues.apache.org/jira/browse/IGNITE-16334
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Evgeny Stanilovsky
> Priority: Major
> Labels: calcite, calcite2-required, ignite-3
>
> 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.
> {noformat}
> MergeJoinConverterRule.INSTANCE,
> CorrelatedNestedLoopJoinRule.INSTANCE,
> CorrelateToNestedLoopRule.INSTANCE,
> NestedLoopJoinConverterRule.INSTANCE,
> {noformat}
> Seems [1] can point out the root of such a problem.
> [1] https://issues.apache.org/jira/browse/CALCITE-4542
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
