You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "xiong duan (Jira)" <ji...@apache.org> on 2022/05/12 23:13:00 UTC
[jira] [Assigned] (CALCITE-5139) Improve Join print plan to add the CorrelationId info
[ https://issues.apache.org/jira/browse/CALCITE-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
xiong duan reassigned CALCITE-5139:
-----------------------------------
Assignee: xiong duan
> Improve Join print plan to add the CorrelationId info
> -----------------------------------------------------
>
> Key: CALCITE-5139
> URL: https://issues.apache.org/jira/browse/CALCITE-5139
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.30.0
> Reporter: xiong duan
> Assignee: xiong duan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.31.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When the Filter plan has CorrelationId info, The Filter output plan will be:
> {noformat}
> LogicalFilter(condition=[=($10, $SCALAR_QUERY({
> LogicalAggregate(group=[{}], EXPR$0=[MAX($0)])
> LogicalProject(NAME=[$1])
> LogicalFilter(condition=[=($0, $cor0.DEPTNO0)])
> LogicalTableScan(table=[[CATALOG, SALES, DEPT]])
> }))], variablesSet=[[$cor0]]){noformat}
> This plan makes the user know this plan includes the variables set. But when the Join include the CorrelationId info, it didn't output it.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)