beyond1920 opened a new pull request #8010: [FLINK-11949][table-planner-blink] Introduce ExecNode to blink planner URL: https://github.com/apache/flink/pull/8010 [##](url) What is the purpose of the change *The pr introduce 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. * ## Brief change log - * Add ExecNode * - * Add BatchExecNode, StreamExecNode* - * Add ExecNodeVisitor to visit a ExecNode graph* ## Verifying this change This change only introduce interfaces, not add any implementation yet, so the pr without any test coverage. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (yes) - If yes, how is the feature documented? (JavaDocs)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
