[
https://issues.apache.org/jira/browse/FLINK-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt Young closed FLINK-12079.
------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
fixed in 79d09b5ab04aa60e26cb2fd529c5469f840edcd2
> Add support for generating optimized logical plan for join on batch
> -------------------------------------------------------------------
>
> Key: FLINK-12079
> URL: https://issues.apache.org/jira/browse/FLINK-12079
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
> Reporter: godfrey he
> Assignee: godfrey he
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, there are 3 types of batch physical join nodes:
> {{BatchExecHashJoin}}, {{BatchExecSortMergeJoin}} and
> {{BatchExecNestedLoopJoin}}. This issue aims to add rules to convert logical
> join to appropriate physical join.
> a logical join
> * can be converted to {{BatchExecHashJoin}} if there exists at least one
> equal-join condition and ShuffleHashJoin or BroadcastHashJoin are enabled,
> * can be converted to {{BatchExecSortMergeJoin}} if there exists at least one
> equal-join condition and SortMergeJoin is enabled,
> * can be converted to {{BatchExecNestedLoopJoin}} if NestedLoopJoin is
> enabled or one of join input sides returns at most a single row.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
