[ https://issues.apache.org/jira/browse/FLINK-37890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther updated FLINK-37890: --------------------------------- Summary: Extend FlinkLogicalMultiJoin to check for common join key (was: FLIP-516: Extend FlinkLogicalMultiJoin to check for common join key) > Extend FlinkLogicalMultiJoin 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 > Priority: Major > > We need to 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]. > * Add Rule 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 9 chained joins, 3 have one common key and 6 have another will generate > two chained multi joins. > ** This could be addressed in the new FlinkLogicalMultiJoin produced by > FLINK-37889 > Related: > * Add FlinkLogicalMultiJoin with all parameters we need + > FlinkJoinToFlinkMultiJoinRule to create it > -- This message was sent by Atlassian Jira (v8.20.10#820010)