[
https://issues.apache.org/jira/browse/FLINK-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699374#comment-14699374
]
Stephan Ewen commented on FLINK-2415:
-------------------------------------
The plan is currently created from the Optimizer Plan, which has different
vertices than the actual runtime graph (due to iterations, chaining).
I would change the generation of the runtime plan as follows:
- The JSON plan is generated for / by the JobGraph
- Extra JSON information may be attached to each JobVertex and each input,
such that the optimizer make its information available to the runtime dashboard.
That way, each node in the JSON graph is naturally linked to the execution
statistics by the {{JobVertexID}}
> Link nodes in plan to vertices
> ------------------------------
>
> Key: FLINK-2415
> URL: https://issues.apache.org/jira/browse/FLINK-2415
> Project: Flink
> Issue Type: Sub-task
> Components: Webfrontend
> Reporter: Piotr Godek
> Assignee: Stephan Ewen
>
> The plan API function (/jobs/<jobid>/plan) lacks vertices' identifiers, so
> that plan can be linked to execution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
