[
https://issues.apache.org/jira/browse/IGNITE-16493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17948450#comment-17948450
]
Evgeny Stanilovsky commented on IGNITE-16493:
---------------------------------------------
this issue will fix a mentioned case [1]
[1] https://issues.apache.org/jira/browse/CALCITE-6962
> Calcite engine. Decorrelation after subquery rewrite
> ----------------------------------------------------
>
> Key: IGNITE-16493
> URL: https://issues.apache.org/jira/browse/IGNITE-16493
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Aleksey Plekhanov
> Priority: Major
> Labels: calcite, calcite2-required, calcite3-required
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently decorrelation is performed in {{SqlToRelConverter}}, but after this
> {{PlannerPhase.HEP_DECORRELATE}} planning phase is executed (which actually
> rewrites subqueries into correlates, but doesn't perform decorrelation). In
> some cases, other types of join can cost less than correlated nested loop
> join, so we can try to decorrelate the query plan again after
> {{PlannerPhase.HEP_DECORRELATE}} phase (call
> {{RelDecorrelator.decorrelateQuery}}).
> {{PlannerPhase.HEP_DECORRELATE}} should be also renamed to something like
> "HEP_REWRITE_SUBQUERY".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
