You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2022/07/19 07:52:00 UTC
[jira] [Commented] (FLINK-28599) Adding FlinkJoinToMultiJoinRule to support translating left/right outer join to multi join
[ https://issues.apache.org/jira/browse/FLINK-28599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568404#comment-17568404 ]
Martijn Visser commented on FLINK-28599:
----------------------------------------
[~337361684@qq.com] Do you know if this is addressed in a later version of Calcite already? If not, it probably makes sense to also raise this issue with the Calcite community?
> Adding FlinkJoinToMultiJoinRule to support translating left/right outer join to multi join
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-28599
> URL: https://issues.apache.org/jira/browse/FLINK-28599
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Affects Versions: 1.16.0
> Reporter: Yunhong Zheng
> Assignee: Yunhong Zheng
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> Now, Flink use Calcite's rule
> {code:java}
> JOIN_TO_MULTI_JOIN{code}
> to convert multiple joins into a join set, which can be used by join reorder. However, calcite's rule can not adapte to all outer joins. For left or right outer join, if they meet certain conditions, it can also be converted to multi join.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)