You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Junrui Lee (Jira)" <ji...@apache.org> on 2025/01/16 05:03:00 UTC

[jira] [Resolved] (FLINK-37139) Improve AdaptiveSkewedJoinOptimizationStrategy to make it effective in more scenarios

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

Junrui Lee resolved FLINK-37139.
--------------------------------
    Fix Version/s: 2.0.0
       Resolution: Fixed

master d774cf1bdeac654b35993f43718e4fdc68f129cc

> Improve AdaptiveSkewedJoinOptimizationStrategy to make it effective in more scenarios
> -------------------------------------------------------------------------------------
>
>                 Key: FLINK-37139
>                 URL: https://issues.apache.org/jira/browse/FLINK-37139
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Lei Yang
>            Assignee: Lei Yang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>
> Currently, the scenarios in which the AdaptiveSkewedJoinOptimizationStrategy is effective are too limited. For example, when there is an output edge of the forward for unspecified type, the optimization cannot be applied. However, this optimization wouldn't break the data correctness of this kind output edges. Therefore, we will optimize this scenario to enable the optimization to be effective in more scenarios.



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