This is an automated email from the ASF dual-hosted git repository. chesnay pushed a commit to branch release-1.9 in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/release-1.9 by this push: new b9ce2a1 [FLINK-13862][docs] Update execution plans docs b9ce2a1 is described below commit b9ce2a19629d2f5a006afd30d2c43457a36dbd33 Author: Chesnay Schepler <ches...@apache.org> AuthorDate: Fri Dec 6 17:19:32 2019 +0100 [FLINK-13862][docs] Update execution plans docs --- docs/dev/execution_plans.md | 11 ++++------- docs/dev/execution_plans.zh.md | 13 +++++-------- docs/fig/plan_visualizer.png | Bin 145778 -> 140792 bytes 3 files changed, 9 insertions(+), 15 deletions(-) diff --git a/docs/dev/execution_plans.md b/docs/dev/execution_plans.md index 29a3641..a48adc4 100644 --- a/docs/dev/execution_plans.md +++ b/docs/dev/execution_plans.md @@ -28,10 +28,8 @@ useful to know how exactly Flink will execute your program. __Plan Visualization Tool__ -Flink comes packaged with a visualization tool for execution plans. The HTML document containing -the visualizer is located under ```tools/planVisualizer.html```. It takes a JSON representation of -the job execution plan and visualizes it as a graph with complete annotations of execution -strategies. +Flink provides a [visualization tool](https://flink.apache.org/visualizer/) for execution plans, which takes a JSON +representation of the job execution plan and visualizes it as a graph with complete annotations of execution strategies. The following code shows how to print the execution plan JSON from your program: @@ -59,7 +57,7 @@ println(env.getExecutionPlan()) To visualize the execution plan, do the following: -1. **Open** ```planVisualizer.html``` with your web browser, +1. **Open** the [visualizer](https://flink.apache.org/visualizer/) with your web browser, 2. **Paste** the JSON string into the text field, and 3. **Press** the draw button. @@ -71,8 +69,7 @@ After these steps, a detailed execution plan will be visualized. __Web Interface__ Flink offers a web interface for submitting and executing jobs. The interface is part of the JobManager's -web interface for monitoring, per default running on port 8081. Job submission via this interfaces requires -that you have set `web.submit.enable: true` in `flink-conf.yaml`. +web interface for monitoring, per default running on port 8081. You may specify program arguments before the job is executed. The plan visualization enables you to show the execution plan before executing the Flink job. diff --git a/docs/dev/execution_plans.zh.md b/docs/dev/execution_plans.zh.md index eefa8f4..a48adc4 100644 --- a/docs/dev/execution_plans.zh.md +++ b/docs/dev/execution_plans.zh.md @@ -1,5 +1,5 @@ --- -title: "执行计划" +title: "Execution Plans" nav-parent_id: execution nav-pos: 40 --- @@ -28,10 +28,8 @@ useful to know how exactly Flink will execute your program. __Plan Visualization Tool__ -Flink comes packaged with a visualization tool for execution plans. The HTML document containing -the visualizer is located under ```tools/planVisualizer.html```. It takes a JSON representation of -the job execution plan and visualizes it as a graph with complete annotations of execution -strategies. +Flink provides a [visualization tool](https://flink.apache.org/visualizer/) for execution plans, which takes a JSON +representation of the job execution plan and visualizes it as a graph with complete annotations of execution strategies. The following code shows how to print the execution plan JSON from your program: @@ -59,7 +57,7 @@ println(env.getExecutionPlan()) To visualize the execution plan, do the following: -1. **Open** ```planVisualizer.html``` with your web browser, +1. **Open** the [visualizer](https://flink.apache.org/visualizer/) with your web browser, 2. **Paste** the JSON string into the text field, and 3. **Press** the draw button. @@ -71,8 +69,7 @@ After these steps, a detailed execution plan will be visualized. __Web Interface__ Flink offers a web interface for submitting and executing jobs. The interface is part of the JobManager's -web interface for monitoring, per default running on port 8081. Job submission via this interfaces requires -that you have set `web.submit.enable: true` in `flink-conf.yaml`. +web interface for monitoring, per default running on port 8081. You may specify program arguments before the job is executed. The plan visualization enables you to show the execution plan before executing the Flink job. diff --git a/docs/fig/plan_visualizer.png b/docs/fig/plan_visualizer.png index 85b8c55..c9b5731 100644 Binary files a/docs/fig/plan_visualizer.png and b/docs/fig/plan_visualizer.png differ