flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dian Fu (Jira)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-16165) NestedLoopJoin fallback to HashJoin when build records number is very large
Date Wed, 11 Nov 2020 03:20:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-16165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229680#comment-17229680
] 

Dian Fu commented on FLINK-16165:
---------------------------------

Hi [~danny0405] [~lzljs3620320] Are we still planning to make this into the 1.12.0 release?



> 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 / Planner
>            Reporter: Jingsong Lee
>            Assignee: Jingsong Lee
>            Priority: Critical
>             Fix For: 1.12.0
>
>
> 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.3.4#803005)

Mime
View raw message