You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dawid Wysakowicz (Jira)" <ji...@apache.org> on 2025/06/02 12:44:00 UTC

[jira] [Closed] (FLINK-37481) FLIP-516: Multi way join operator

     [ https://issues.apache.org/jira/browse/FLINK-37481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dawid Wysakowicz closed FLINK-37481.
------------------------------------
    Fix Version/s: 2.1.0
       Resolution: Implemented

Implemented in cf55d306f570134e2d3d332a0acba7d8737c87b7

> FLIP-516: Multi way join operator
> ---------------------------------
>
>                 Key: FLINK-37481
>                 URL: https://issues.apache.org/jira/browse/FLINK-37481
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Gustavo de Morais
>            Assignee: Gustavo de Morais
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.1.0
>
>
> We currently always rely on a chain of binary joins when there are multiple joins in a query. This can often generate a lot of intermediate state which considerably increases the state size - specially for regular joins. There are optimizations that can be done to a multi-way join operator that can optimize the worst case scenarios of binary joins.
>  
> We want as a first step with this ticket to have a multi join operator that works on multiple inputs for streaming regular joins.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)