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

Posted to issues@flink.apache.org by "Bonnie Varghese (Jira)" <ji...@apache.org> on 2026/09/08 19:09:00 UTC

[jira] [Assigned] (FLINK-16165) NestedLoopJoin fallback to HashJoin when build records number is very large

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

Bonnie Varghese reassigned FLINK-16165:
---------------------------------------

    Assignee: Bonnie Varghese

> NestedLoopJoin fallback to HashJoin when build records number is very large
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-16165
>                 URL: https://issues.apache.org/jira/browse/FLINK-16165
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Runtime
>            Reporter: Jingsong Lee
>            Assignee: Bonnie Varghese
>            Priority: Not a Priority
>              Labels: auto-deprioritized-critical, auto-deprioritized-major, auto-deprioritized-minor
>
> Now, if the statistic is not so accurate, maybe choose wrong join type to nested loop join.
> If build records number is very large, this lead to very slow join, the user looks like the join is in Hang.
> It is a stability problem, We should fallback to hash join in runtime to avoid this hang.



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