[ 
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 stale-minor  
(was: auto-deprioritized-critical auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> 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: Minor
>              Labels: auto-deprioritized-critical, auto-deprioritized-major, 
> stale-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)

Reply via email to