[
https://issues.apache.org/jira/browse/CALCITE-7071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17985895#comment-17985895
]
Zhen Chen commented on CALCITE-7071:
------------------------------------
OK, I will wait for Jira discussion next time. This is mainly a minor change,
and it is basically completed during the verification process. Why is it placed
in ProjectJoinRemoveRule? It refers to a situation in [Outer Join Elimination
in the Teradata
RDBMS|https://link.springer.com/chapter/10.1007/978-3-540-30075-5_70]. But this
scenario does not really require a Project. So would it be better if I
implement a new rule for OuterJoinRemoveRule(contains LEFT JOIN and RIGHT JOIN)?
> Support replacing JOIN node with its child node when JOIN condition is false
> in ProjectJoinRemoveRule
> -----------------------------------------------------------------------------------------------------
>
> Key: CALCITE-7071
> URL: https://issues.apache.org/jira/browse/CALCITE-7071
> Project: Calcite
> Issue Type: Improvement
> Reporter: Zhen Chen
> Assignee: Zhen Chen
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.41.0
>
>
> SQL
> {code:java}
> SELECT e.deptno
> FROM sales.emp e
> LEFT JOIN sales.dept d ON e.deptno = d.deptno and e.deptno between 3 and 1
> {code}
> Plan before
> {code:java}
> LogicalProject(DEPTNO=[$7])
> LogicalJoin(condition=[false], joinType=[left])
> LogicalTableScan(table=[[CATALOG, SALES, EMP]])
> LogicalTableScan(table=[[CATALOG, SALES, DEPT]])
> {code}
> Plan after
> {code:java}
> LogicalProject(DEPTNO=[$7])
> LogicalTableScan(table=[[CATALOG, SALES, EMP]])
> {code}
> In ProjectJoinRemoveRule, when the Join condition is false, replace the Join
> with its left child for a left join or its right child for a right join. The
> above is an example of a left join.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
