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/02/19 10:50:00 UTC
[jira] [Created] (FLINK-16165) NestedLoopJoin fallback to HashJoin
when build records number is very large
Jingsong Lee created FLINK-16165:
------------------------------------
Summary: 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
Fix For: 1.11.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)