[FLINK-11946] Introduce ExecNode

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Fix Version/s: 1.9.0
• Component/s: Table SQL / Planner
• Labels: pull-request-available
• Assignee: Jing Zhang
• Reporter: Jing Zhang
• Created: 18/Mar/19 04:11
• Updated: 27/Jan/22 17:43
• Resolved: 20/Mar/19 02:26

Description

This issue introduces ExecNode. ExecNode and FlinkPhysicalRel plays different role. FlinkPhysicalRel is a physical relational expression, while ExecNode is a representation of execution information, such as how much resource the node will take, how to convert to StreamTransformation.
It should be noticed that FlinkPhysicalRel and ExecNode could be implemented by a same concrete physical node, such as StreamExecCalc, StreamExecScan, etc. The interface exposed by a concrete physical node is different at different stages. A FlinkPhysicalRel DAG is generated after physical optimization, then translate the plan to ExecNode DAG. All post processors all apply on ExecNode DAG, such as detect deadlock, set heap/memory/cpu, etc.

Issue Links

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