[
https://issues.apache.org/jira/browse/CALCITE-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17725670#comment-17725670
]
Benchao Li commented on CALCITE-5720:
-------------------------------------
It's interesting that JoinPushTransitivePredicatesRule is not in the default
core rule set, does anyone know the reason why? To me, this will be a good
candidate for default rule set.
> improve FilterJoinRule to push filter into both join sides
> ----------------------------------------------------------
>
> Key: CALCITE-5720
> URL: https://issues.apache.org/jira/browse/CALCITE-5720
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Suhan Mao
> Priority: Major
>
> In flink source code,
> [FlinkFilterJoinRule|https://github.com/apache/flink/blob/master/flink-table/flink-table-planner/src/main/java/org/apache/flink/table/planner/plan/rules/logical/FlinkFilterJoinRule.java],
> the FilterJoinRule is improved to handle more cases:
> for the above filter of inner/left/right join or the join condition of inner
> join, the predicate which field references are all from one side join
> condition can be pushed into another join side. Such as:
> `SELECT * FROM MyTable1 join MyTable2 ON a1 = a2 AND a1 = 2`
> `SELECT * FROM MyTable1, MyTable2 WHERE a1 = a2 AND a1 = 2 `
>
> I would like to add the improvement to exist FilterJoinRule class.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
