You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jingsong Lee (Jira)" <ji...@apache.org> on 2020/11/11 03:38:00 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17229698#comment-17229698 ]
Jingsong Lee edited comment on FLINK-16165 at 11/11/20, 3:37 AM:
-----------------------------------------------------------------
[~dian.fu] I have moved this to 1.13
was (Author: lzljs3620320):
[~dian.fu] I moved this to 1.13
> 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.13.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)