[
https://issues.apache.org/jira/browse/FLINK-34535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17822390#comment-17822390
]
lincoln lee commented on FLINK-34535:
-------------------------------------
[~heigebupahei] The current `explain` syntax is just for showing the planinfo,
if we want to override something to the real plan which is for execution, I
suggest to extend current compiled plan, as we have such ways to compile a
query and execute the compiled plan:
{{{}{}}}{{{}{}}}
{code:java}
COMPILE PLAN FOR '<your_path.json>' <insert_query>
EXECUTE PLAN FOR '<your_path.json>'{code}
(Also adding new mode to current `ExplainDetail` is a public api change, there
should be a
[FLIP|https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals?src=contextnavpagetreemode]
discussion）
Regarding to the motivation 'combine it with the parameter
`pipeline.jobvertex-parallelism-overrides` to set up my task parallelism',
could you explain more about it？
{{}}
> Support JobPlanInfo for the explain result
> ------------------------------------------
>
> Key: FLINK-34535
> URL: https://issues.apache.org/jira/browse/FLINK-34535
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: yuanfenghu
> Priority: Major
> Labels: pull-request-available
>
> In the Flink Sql Explain syntax, we can set ExplainDetails to plan
> JSON_EXECUTION_PLAN, but we cannot plan JobPlanInfo. If we can explain this
> part of the information, referring to JobPlanInfo, I can combine it with the
> parameter `pipeline.jobvertex-parallelism-overrides` to set up my task
> parallelism
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
