[ 
https://issues.apache.org/jira/browse/FLINK-11425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-11425:
-----------------------------------
      Labels: auto-deprioritized-major auto-unassigned  (was: auto-unassigned 
stale-major)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so 
it is being deprioritized. If this ticket is actually Major, please raise the 
priority and ask a committer to assign you the issue or revive the public 
discussion.


> Support of “Hash Teams” in Hybrid Hash Join
> -------------------------------------------
>
>                 Key: FLINK-11425
>                 URL: https://issues.apache.org/jira/browse/FLINK-11425
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / Runtime
>            Reporter: Ji Liu
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned
>
> Hybrid Hash Join is already supported in current version. The join starts 
> operating in memory and gradually starts spilling contents to disk, when the 
> memory is not sufficient.
>  
> Current hash join only support two inputs,  so when a job contains multiple 
> hash joins which have the same join keys, it will consume some unnecessary 
> resources (I/O, memory, etc) because some upstream output data may useless 
> for downstream hash join.
>  
> According to the above observations, we want to provide a HashTeamManager to 
> implement multiway inputs hash join by combining several two way hash join 
> which have same join keys. HashTeamManager manage the relations of multiple 
> HashTables and improve efficiency in memory use and lower I/O operations by 
> joining multiple relations at one time.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to