[
https://issues.apache.org/jira/browse/FLINK-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011045#comment-15011045
]
ASF GitHub Bot commented on FLINK-2686:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1378#issuecomment-157724392
The JSON plan generation has actually two points now (that we should try to
consolidate). The other one is on
"https://github.com/apache/flink/blob/6e0e67d2e0d5180d6fba492e8ab9cc8fb18fdf68/flink-runtime/src/main/java/org/apache/flink/runtime/jobgraph/jsonplan/JsonPlanGenerator.java";
and deals with attaching the JSON plan to every JobGraph so that the runtime
dashboard can draw a graph. That plan is a bit different then the optimizer
JSON (because it is not iteration aware and chained tasks are only one operator
any more), but otherwise follows similar logic.
> Extend JSON plan dump to contain channel info
> ---------------------------------------------
>
> Key: FLINK-2686
> URL: https://issues.apache.org/jira/browse/FLINK-2686
> Project: Flink
> Issue Type: Improvement
> Components: Optimizer
> Affects Versions: 0.10.0
> Reporter: Ufuk Celebi
> Assignee: Chesnay Schepler
> Priority: Minor
>
> The execution plan JSON (via {{env.getExecutionPlan()}}) contains no
> information about the data exchange mode of the used channels.
> I think this would be super helpful while debugging problems like FLINK-2685.
> The channel types should also be considered in the plan rendering, but that's
> a separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
