[FLINK-12079] Add support for generating optimized logical plan for join on batch

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.9.0
• Component/s: Table SQL / Planner
• Labels: pull-request-available
• Assignee: godfrey he
• Reporter: godfrey he
• Created: 01/Apr/19 11:25
• Updated: 02/Apr/19 04:14
• Resolved: 02/Apr/19 04:14

Description

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.

Issue Links

• is a child of: FLINK-11488 Add a basic Blink planner framework
• links to: GitHub Pull Request #8094