You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/11/18 15:04:11 UTC
[jira] [Commented] (FLINK-2686) Extend JSON plan dump to contain
channel info
[ https://issues.apache.org/jira/browse/FLINK-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011033#comment-15011033 ]
ASF GitHub Bot commented on FLINK-2686:
---------------------------------------
GitHub user zentol opened a pull request:
https://github.com/apache/flink/pull/1378
[FLINK-2686] Show exchange mode in JSON plan
Extends the PlanJSONDumpGenerator to also include the Data Exchange mode. It will be shown like this:
```
...
"parallelism": "2",
"predecessors": [
{"id": 5, "ship_strategy": "Forward", "exchange_mode": "PIPELINED"}
],
"driver_strategy": "Map",
...
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zentol/flink 2686_json_exchange
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1378.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1378
----
commit 1ce8aa73ef773f20230d272459d5f05f71fef369
Author: zentol <ch...@apache.org>
Date: 2015-11-18T13:52:48Z
[FLINK-2686] Show exchange mode in JSON plan
----
> 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)