You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dmitriy Linevich (Jira)" <ji...@apache.org> on 2026/03/27 06:34:00 UTC
[jira] [Updated] (FLINK-39340) Transform binary multi join back to regular join
[ https://issues.apache.org/jira/browse/FLINK-39340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Linevich updated FLINK-39340:
-------------------------------------
Description:
It has been observed that multi-join optimization leads to performance regressions when the multi join has only two inputs.
!image-2026-03-27-13-33-01-873.png!
*As a result:*
* Q4 - 17% regression
* Q9 - 17% regression
* mini-batch optimization for regular join, but not for multi join
* window mofication for regular join, but not for multi join (Q5)
*Suggestions:*
# Add rule (BinaryMultiJoinToJoinRule) after multi join, that will transform multi join with 2 inputs back to regular join
# Modify JoinToMultiJoinRule, it shouldn't to generate MultiJoin with 2 inputs
was:
It has been observed that multi-join optimization leads to performance regressions when the multi join has only two inputs.
!image-2026-03-27-13-23-35-237.png!
*As a result:*
* Q4 - 17% regression
* Q9 - 17% regression
* mini-batch optimization for regular join, but not for multi join
* window mofication for regular join, but not for multi join (Q5)
*Suggestions:*
# Add rule (BinaryMultiJoinToJoinRule) after multi join, that will transform multi join with 2 inputs back to regular join
# Modify JoinToMultiJoinRule, it shouldn't to generate MultiJoin with 2 inputs
> Transform binary multi join back to regular join
> ------------------------------------------------
>
> Key: FLINK-39340
> URL: https://issues.apache.org/jira/browse/FLINK-39340
> Project: Flink
> Issue Type: Improvement
> Reporter: Dmitriy Linevich
> Priority: Major
> Attachments: image-2026-03-27-13-33-32-140.png
>
>
> It has been observed that multi-join optimization leads to performance regressions when the multi join has only two inputs.
> !image-2026-03-27-13-33-01-873.png!
> *As a result:*
> * Q4 - 17% regression
> * Q9 - 17% regression
> * mini-batch optimization for regular join, but not for multi join
> * window mofication for regular join, but not for multi join (Q5)
>
> *Suggestions:*
> # Add rule (BinaryMultiJoinToJoinRule) after multi join, that will transform multi join with 2 inputs back to regular join
> # Modify JoinToMultiJoinRule, it shouldn't to generate MultiJoin with 2 inputs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)