[
https://issues.apache.org/jira/browse/FLINK-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081355#comment-15081355
]
ASF GitHub Bot commented on FLINK-3192:
---------------------------------------
Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/1477#discussion_r48752174
--- Diff:
flink-core/src/main/java/org/apache/flink/api/common/PlanExecutor.java ---
@@ -129,6 +129,8 @@ public boolean isPrintingStatusDuringExecution() {
*/
public abstract String getOptimizerPlanAsJSON(Plan plan) throws
Exception;
+ public abstract String getOptimizerPlanContext(Plan plan, boolean
extended) throws Exception;
--- End diff --
If we reuse the JSON string (as proposed in my comment at
`ExecutionEnvironment`) we do not need this method either.
> Add explain support to print ast and sql physical execution plan.
> ------------------------------------------------------------------
>
> Key: FLINK-3192
> URL: https://issues.apache.org/jira/browse/FLINK-3192
> Project: Flink
> Issue Type: New Feature
> Components: Table API
> Reporter: GaoLun
> Assignee: GaoLun
> Priority: Minor
> Labels: features
>
> Table API doesn't support sql-explanation now. Add the explain support to
> print ast (abstract syntax tree) and the physical execution plan of sql.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
