You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by sj...@apache.org on 2020/06/10 14:11:29 UTC
[flink] 02/07: [FLINK-17980][docs] Rename Hands-on Training to
Learn Flink
This is an automated email from the ASF dual-hosted git repository.
sjwiesman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
commit 5df38371cf05efb87bc9645325036c80b26e3983
Author: Seth Wiesman <sj...@gmail.com>
AuthorDate: Mon Jun 8 11:35:19 2020 -0500
[FLINK-17980][docs] Rename Hands-on Training to Learn Flink
---
docs/{training => learn-flink}/datastream_api.md | 2 +-
docs/{training => learn-flink}/datastream_api.zh.md | 2 +-
docs/{training => learn-flink}/etl.md | 2 +-
docs/{training => learn-flink}/etl.zh.md | 2 +-
docs/{training => learn-flink}/event_driven.md | 8 ++++----
docs/{training => learn-flink}/event_driven.zh.md | 8 ++++----
docs/{training => learn-flink}/fault_tolerance.md | 6 +++---
docs/{training => learn-flink}/fault_tolerance.zh.md | 6 +++---
docs/{training => learn-flink}/index.md | 6 +++---
docs/{training => learn-flink}/index.zh.md | 0
docs/{training => learn-flink}/streaming_analytics.md | 8 ++++----
docs/{training => learn-flink}/streaming_analytics.zh.md | 8 ++++----
12 files changed, 29 insertions(+), 29 deletions(-)
diff --git a/docs/training/datastream_api.md b/docs/learn-flink/datastream_api.md
similarity index 99%
rename from docs/training/datastream_api.md
rename to docs/learn-flink/datastream_api.md
index 7392041..fe6f548 100644
--- a/docs/training/datastream_api.md
+++ b/docs/learn-flink/datastream_api.md
@@ -3,7 +3,7 @@ title: Intro to the DataStream API
nav-id: datastream-api
nav-pos: 2
nav-title: Intro to the DataStream API
-nav-parent_id: training
+nav-parent_id: learn-flink
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
diff --git a/docs/training/datastream_api.zh.md b/docs/learn-flink/datastream_api.zh.md
similarity index 99%
rename from docs/training/datastream_api.zh.md
rename to docs/learn-flink/datastream_api.zh.md
index b5f7606..5bc25bd 100644
--- a/docs/training/datastream_api.zh.md
+++ b/docs/learn-flink/datastream_api.zh.md
@@ -3,7 +3,7 @@ title: DataStream API 简介
nav-id: datastream-api
nav-pos: 2
nav-title: DataStream API 简介
-nav-parent_id: training
+nav-parent_id: learn-flink
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
diff --git a/docs/training/etl.md b/docs/learn-flink/etl.md
similarity index 99%
rename from docs/training/etl.md
rename to docs/learn-flink/etl.md
index 9337be3..29cbdbf 100644
--- a/docs/training/etl.md
+++ b/docs/learn-flink/etl.md
@@ -3,7 +3,7 @@ title: Data Pipelines & ETL
nav-id: etl
nav-pos: 3
nav-title: Data Pipelines & ETL
-nav-parent_id: training
+nav-parent_id: learn-flink
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
diff --git a/docs/training/etl.zh.md b/docs/learn-flink/etl.zh.md
similarity index 99%
rename from docs/training/etl.zh.md
rename to docs/learn-flink/etl.zh.md
index b0b456e..667f2f0 100644
--- a/docs/training/etl.zh.md
+++ b/docs/learn-flink/etl.zh.md
@@ -3,7 +3,7 @@ title: Data Pipelines & ETL
nav-id: etl
nav-pos: 3
nav-title: Data Pipelines & ETL
-nav-parent_id: training
+nav-parent_id: learn-flink
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
diff --git a/docs/training/event_driven.md b/docs/learn-flink/event_driven.md
similarity index 97%
rename from docs/training/event_driven.md
rename to docs/learn-flink/event_driven.md
index 408ab42..4d4592c 100644
--- a/docs/training/event_driven.md
+++ b/docs/learn-flink/event_driven.md
@@ -3,7 +3,7 @@ title: Event-driven Applications
nav-id: event-driven
nav-pos: 5
nav-title: Event-driven Applications
-nav-parent_id: training
+nav-parent_id: learn-flink
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
@@ -38,8 +38,8 @@ with Flink. It is very similar to a `RichFlatMapFunction`, but with the addition
### Example
If you've done the
-[hands-on exercise]({% link training/streaming_analytics.md %}#hands-on)
-in the [Streaming Analytics training]({% link training/streaming_analytics.md %}),
+[hands-on exercise]({% link learn-flink/streaming_analytics.md %}#hands-on)
+in the [Streaming Analytics training]({% link learn-flink/streaming_analytics.md %}),
you will recall that it uses a `TumblingEventTimeWindow` to compute the sum of the tips for
each driver during each hour, like this:
@@ -177,7 +177,7 @@ Things to consider:
* What happens with late events? Events that are behind the watermark (i.e., late) are being
dropped. If you want to do something better than this, consider using a side output, which is
- explained in the [next section]({% link training/event_driven.md
+ explained in the [next section]({% link learn-flink/event_driven.md
%}#side-outputs).
* This example uses a `MapState` where the keys are timestamps, and sets a `Timer` for that same
diff --git a/docs/training/event_driven.zh.md b/docs/learn-flink/event_driven.zh.md
similarity index 98%
rename from docs/training/event_driven.zh.md
rename to docs/learn-flink/event_driven.zh.md
index 6c2c39d..fd848c9 100644
--- a/docs/training/event_driven.zh.md
+++ b/docs/learn-flink/event_driven.zh.md
@@ -3,7 +3,7 @@ title: 事件驱动应用
nav-id: 事件驱动
nav-pos: 5
nav-title: 事件驱动应用
-nav-parent_id: training
+nav-parent_id: learn-flink
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
@@ -37,8 +37,8 @@ under the License.
### 示例
如果你已经体验了
-[流式分析训练]({% link training/streaming_analytics.zh.md %})
-的[动手实践]({% link training/streaming_analytics.zh.md %}#hands-on)，
+[流式分析训练]({% link learn-flink/streaming_analytics.zh.md %})
+的[动手实践]({% link learn-flink/streaming_analytics.zh.md %}#hands-on)，
你应该记得，它是采用 `TumblingEventTimeWindow` 来计算每个小时内每个司机的小费总和，
像下面的示例这样：
@@ -173,7 +173,7 @@ public void processElement(
* 延迟的事件怎么处理？watermark 后面的事件（即延迟的）正在被删除。
如果你想做一些比这更高级的操作，可以考虑使用旁路输出（Side outputs），这将在[下一节]({% link
- training/event_driven.zh.md%}#side-outputs)中解释。
+ learn-flink/event_driven.zh.md%}#side-outputs)中解释。
* 本例使用一个 `MapState`，其中 keys 是时间戳（timestamp），并为同一时间戳设置一个 Timer。
这是一种常见的模式；它使得在 Timer 触发时查找相关信息变得简单高效。
diff --git a/docs/training/fault_tolerance.md b/docs/learn-flink/fault_tolerance.md
similarity index 97%
rename from docs/training/fault_tolerance.md
rename to docs/learn-flink/fault_tolerance.md
index ee01c0a..b16610b 100644
--- a/docs/training/fault_tolerance.md
+++ b/docs/learn-flink/fault_tolerance.md
@@ -3,7 +3,7 @@ title: Fault Tolerance via State Snapshots
nav-id: fault-tolerance
nav-pos: 6
nav-title: Fault Tolerance
-nav-parent_id: training
+nav-parent_id: learn-flink
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
@@ -187,9 +187,9 @@ once, the following must be true:
## Hands-on
The [Flink Operations Playground]({% link
-getting-started/docker-playgrounds/flink-operations-playground.md %}) includes a section on
+try-flink/flink-operations-playground.md %}) includes a section on
[Observing Failure & Recovery]({% link
-getting-started/docker-playgrounds/flink-operations-playground.md %}#observing-failure--recovery).
+try-flink/flink-operations-playground.md %}#observing-failure--recovery).
{% top %}
diff --git a/docs/training/fault_tolerance.zh.md b/docs/learn-flink/fault_tolerance.zh.md
similarity index 97%
rename from docs/training/fault_tolerance.zh.md
rename to docs/learn-flink/fault_tolerance.zh.md
index 55a26de..189026a 100644
--- a/docs/training/fault_tolerance.zh.md
+++ b/docs/learn-flink/fault_tolerance.zh.md
@@ -3,7 +3,7 @@ title: Fault Tolerance via State Snapshots
nav-id: fault-tolerance
nav-pos: 6
nav-title: Fault Tolerance
-nav-parent_id: training
+nav-parent_id: learn-flink
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
@@ -187,9 +187,9 @@ once, the following must be true:
## Hands-on
The [Flink Operations Playground]({% link
-getting-started/docker-playgrounds/flink-operations-playground.zh.md %}) includes a section on
+try-flink/flink-operations-playground.zh.md %}) includes a section on
[Observing Failure & Recovery]({% link
-getting-started/docker-playgrounds/flink-operations-playground.zh.md %}#observing-failure--recovery).
+try-flink/flink-operations-playground.zh.md %}#observing-failure--recovery).
{% top %}
diff --git a/docs/training/index.md b/docs/learn-flink/index.md
similarity index 99%
rename from docs/training/index.md
rename to docs/learn-flink/index.md
index 3707487..f17bdfb 100644
--- a/docs/training/index.md
+++ b/docs/learn-flink/index.md
@@ -1,8 +1,8 @@
---
-title: Hands-on Training
-nav-id: training
+title: Learn Flink
+nav-id: learn-flink
nav-pos: 2
-nav-title: '<i class="fa fa-hand-paper-o title appetizer" aria-hidden="true"></i> Hands-on Training'
+nav-title: '<i class="fa fa-hand-paper-o title appetizer" aria-hidden="true"></i> Learn Flink'
nav-parent_id: root
nav-show_overview: true
---
diff --git a/docs/training/index.zh.md b/docs/learn-flink/index.zh.md
similarity index 100%
rename from docs/training/index.zh.md
rename to docs/learn-flink/index.zh.md
diff --git a/docs/training/streaming_analytics.md b/docs/learn-flink/streaming_analytics.md
similarity index 98%
rename from docs/training/streaming_analytics.md
rename to docs/learn-flink/streaming_analytics.md
index 7dc0503..8263bb6 100644
--- a/docs/training/streaming_analytics.md
+++ b/docs/learn-flink/streaming_analytics.md
@@ -3,7 +3,7 @@ title: Streaming Analytics
nav-id: analytics
nav-pos: 4
nav-title: Streaming Analytics
-nav-parent_id: training
+nav-parent_id: learn-flink
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
@@ -60,7 +60,7 @@ env.setStreamTimeCharacteristic(TimeCharacteristic.EventTime);
If you want to use event time, you will also need to supply a Timestamp Extractor and Watermark
Generator that Flink will use to track the progress of event time. This will be covered in the
section below on [Working with Watermarks]({% link
-training/streaming_analytics.md %}#working-with-watermarks), but first we should explain what
+learn-flink/streaming_analytics.md %}#working-with-watermarks), but first we should explain what
watermarks are.
### Watermarks
@@ -253,7 +253,7 @@ that behavior yourself with a custom Trigger.
A global window assigner assigns every event (with the same key) to the same global window. This is
only useful if you are going to do your own custom windowing, with a custom Trigger. In many cases
where this might seem useful you will be better off using a `ProcessFunction` as described
-[in another section]({% link training/event_driven.md %}#process-functions).
+[in another section]({% link learn-flink/event_driven.md %}#process-functions).
### Window Functions
@@ -365,7 +365,7 @@ the window API that give you more control over this.
You can arrange for the events that would be dropped to be collected to an alternate output stream
instead, using a mechanism called
-[Side Outputs]({% link training/event_driven.md %}#side-outputs).
+[Side Outputs]({% link learn-flink/event_driven.md %}#side-outputs).
Here is an example of what that might look like:
{% highlight java %}
diff --git a/docs/training/streaming_analytics.zh.md b/docs/learn-flink/streaming_analytics.zh.md
similarity index 98%
rename from docs/training/streaming_analytics.zh.md
rename to docs/learn-flink/streaming_analytics.zh.md
index 27544ff..65fbe43 100644
--- a/docs/training/streaming_analytics.zh.md
+++ b/docs/learn-flink/streaming_analytics.zh.md
@@ -3,7 +3,7 @@ title: Streaming Analytics
nav-id: analytics
nav-pos: 4
nav-title: Streaming Analytics
-nav-parent_id: training
+nav-parent_id: learn-flink
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
@@ -60,7 +60,7 @@ env.setStreamTimeCharacteristic(TimeCharacteristic.EventTime);
If you want to use event time, you will also need to supply a Timestamp Extractor and Watermark
Generator that Flink will use to track the progress of event time. This will be covered in the
section below on [Working with Watermarks]({% link
-training/streaming_analytics.zh.md %}#working-with-watermarks), but first we should explain what
+learn-flink/streaming_analytics.zh.md %}#working-with-watermarks), but first we should explain what
watermarks are.
### Watermarks
@@ -253,7 +253,7 @@ that behavior yourself with a custom Trigger.
A global window assigner assigns every event (with the same key) to the same global window. This is
only useful if you are going to do your own custom windowing, with a custom Trigger. In many cases
where this might seem useful you will be better off using a `ProcessFunction` as described
-[in another section]({% link training/event_driven.zh.md %}#process-functions).
+[in another section]({% link learn-flink/event_driven.zh.md %}#process-functions).
### Window Functions
@@ -365,7 +365,7 @@ the window API that give you more control over this.
You can arrange for the events that would be dropped to be collected to an alternate output stream
instead, using a mechanism called
-[Side Outputs]({% link training/event_driven.zh.md %}#side-outputs).
+[Side Outputs]({% link learn-flink/event_driven.zh.md %}#side-outputs).
Here is an example of what that might look like:
{% highlight java %}