[
https://issues.apache.org/jira/browse/FLINK-37890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gustavo de Morais closed FLINK-37890.
-------------------------------------
Resolution: Fixed
Fixed in apache/flink:master 615e19bacba9fede61c6e73bad789d5dea2c2835
> Extend JoinToMultiJoinRule to check for common join key
> -------------------------------------------------------
>
> Key: FLINK-37890
> URL: https://issues.apache.org/jira/browse/FLINK-37890
> Project: Flink
> Issue Type: Sub-task
> Reporter: Gustavo de Morais
> Assignee: Stepan Stepanishchev
> Priority: Major
> Fix For: 2.1.0
>
>
> We should have the optimizer check if it's possible to use a
> StreamingMultiJoinOperator according the [common key
> restrictions|https://cwiki.apache.org/confluence/display/FLINK/FLIP-516%3A+Multi-Way+Join+Operator].
> * Adjust JoinToMultiJoinRule to check if the join chain respects the multi
> join common key restrictions
> * If not, create one multi join for each group of joins that respect. That
> means for example, for 9 chained joins, 3 have one common key and 6 have
> another will generate two chained multi joins
> * This could be done by adjusting the canCombine method to fit our
> requirements
> [https://github.com/apache/flink/blob/fdf0bc7e02380e92bb9ab59e5eb847776372df81/flink-table/flink-table-planner/src/main/java/org/apache/flink/table/planner/plan/rules/logical/JoinToMultiJoinRule.java#L476]
>
> Currently, we'll produce one multi join and the physical rule will fail
> because it can't find a common join key.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
