You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/01/03 22:39:00 UTC
[jira] [Updated] (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 ]
Flink Jira Bot updated FLINK-16165:
-----------------------------------
Labels: auto-deprioritized-critical auto-deprioritized-major auto-deprioritized-minor (was: auto-deprioritized-critical auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.
> 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
> 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.1#820001)