[ 
https://issues.apache.org/jira/browse/CALCITE-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Silun Dong updated CALCITE-7414:
--------------------------------
    Description: After decorrelating a node, we need to determine which output 
column replaces outer variable (i.e. populate the map from {{CorDef}} to output 
index in new node). When decorrelating a Join, we have to take the join type 
into account to decide which side of the Join to use for the replacement (refer 
to section 3.3 in {_}Improving Unnesting of Complex Queries{_}). The current 
implementation omits this logic. The corresponding test case can be found in 
CALCITE-7379.  (was: After decorrelating a node, we need to determine which 
output column replaces outer variable (i.e. populate the map from {{CorDef}} to 
output index in new node). When decorrelating a Join, we have to take the join 
type into account to decide which side of the join to use for the replacement 
(refer to section 3.3 in {_}Improving Unnesting of Complex Queries{_}). The 
current implementation omits this logic. The corresponding test case can be 
found in CALCITE-7379.)

> Incorrect mapping of CorDef after decorrelating a Join in 
> TopDownGeneralDecorrelator
> ------------------------------------------------------------------------------------
>
>                 Key: CALCITE-7414
>                 URL: https://issues.apache.org/jira/browse/CALCITE-7414
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.41.0
>            Reporter: Silun Dong
>            Assignee: Silun Dong
>            Priority: Major
>
> After decorrelating a node, we need to determine which output column replaces 
> outer variable (i.e. populate the map from {{CorDef}} to output index in new 
> node). When decorrelating a Join, we have to take the join type into account 
> to decide which side of the Join to use for the replacement (refer to section 
> 3.3 in {_}Improving Unnesting of Complex Queries{_}). The current 
> implementation omits this logic. The corresponding test case can be found in 
> CALCITE-7379.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to