godfreyhe opened a new pull request #14315: URL: https://github.com/apache/flink/pull/14315
## What is the purpose of the change *As discussed in [FLINK-20478](https://issues.apache.org/jira/browse/FLINK-20478), this pr aims to adjust the explain result as following: So I suggest to make the following adjustments: 1. Keep "Abstract Syntax Tree" as it, which represents the original (un-optimized) RelNode graph converted from SqlNode. 2. Rename "Optimized Logical Plan" to "Optimized Physical Plan", which represents the optimized physical RelNode graph composed of FlinkPhysicalRel. 3.Replace "Physical Execution Plan" with "Optimized Execution Plan", which represents the optimized ExecNode graph. Because "Physical Execution Plan" is not very useful to users.* ## Brief change log *(for example:)* - *Adjust the explain result for blink planner* - *[hotfix] BatchExecRank#explainTerms should use `RelWriter#input` instead of `RelWriter#item` for input rel* - *ExecNodePlanDumper only displays the attributes of ExecNode* ## Verifying this change This change is already covered by existing tests, such as *ExplainTest*. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (yes / **no**) - If yes, how is the feature documented? (not applicable / **docs** / JavaDocs / not documented) ---------------------------------------------------------------- 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: us...@infra.apache.org
