You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by ch...@apache.org on 2021/05/09 21:22:38 UTC
[flink] branch master updated: [hotfix][docs] Fix image links
This is an automated email from the ASF dual-hosted git repository.
chesnay pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new a8d53cf [hotfix][docs] Fix image links
a8d53cf is described below
commit a8d53cf462854d51b18314af24c9f74cb1202f7c
Author: mans2singh <ma...@users.noreply.github.com>
AuthorDate: Sun May 9 17:22:28 2021 -0400
[hotfix][docs] Fix image links
---
docs/content.zh/docs/dev/datastream/sources.md | 6 +++---
docs/content/docs/dev/datastream/sources.md | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/content.zh/docs/dev/datastream/sources.md b/docs/content.zh/docs/dev/datastream/sources.md
index 4228f38..fe5ebfb 100644
--- a/docs/content.zh/docs/dev/datastream/sources.md
+++ b/docs/content.zh/docs/dev/datastream/sources.md
@@ -55,7 +55,7 @@ A Data Source has three core components: *Splits*, the *SplitEnumerator*, and th
The [Source](https://github.com/apache/flink/blob/master/flink-core/src/main/java/org/apache/flink/api/connector/source/Source.java) class is API entry point that ties the above three components together.
-{{< img src="fig/source_components.svg" alt="Illustration of SplitEnumerator and SourceReader interacting" width="70%" >}}
+{{< img src="/fig/source_components.svg" alt="Illustration of SplitEnumerator and SourceReader interacting" width="70%" >}}
**Unified Across Streaming and Batch**
@@ -246,7 +246,7 @@ The `SplitFetcherManager` helps create and maintain a pool of `SplitFetcher`s ea
As an example, as illustrated below, a `SplitFetcherManager` may have a fixed number of threads, each fetching from some splits assigned to the `SourceReader`.
-{{< img width="70%" src="fig/source_reader.svg" alt="One fetcher per split threading model." >}}
+{{< img width="70%" src="/fig/source_reader.svg" alt="One fetcher per split threading model." >}}
The following code snippet implements this threading model.
@@ -378,7 +378,7 @@ Watermark Generators are only active during streaming execution. Batch execution
The data source API supports running watermark generators individually *per split*. That allows Flink to observe the event time progress per split individually, which is important to handle *event time skew* properly and prevent *idle partitions* from holding back the event time progress of the entire application.
-{{< img width="80%" src="fig/per_split_watermarks.svg" alt="Watermark Generation in a Source with two Splits." >}}
+{{< img width="80%" src="/fig/per_split_watermarks.svg" alt="Watermark Generation in a Source with two Splits." >}}
When implementing a source connector using the *Split Reader API*, this is automatically handled. All implementations based on the Split Reader API have split-aware watermarks out-of-the-box.
diff --git a/docs/content/docs/dev/datastream/sources.md b/docs/content/docs/dev/datastream/sources.md
index 3f41977..00c70f8 100644
--- a/docs/content/docs/dev/datastream/sources.md
+++ b/docs/content/docs/dev/datastream/sources.md
@@ -55,7 +55,7 @@ A Data Source has three core components: *Splits*, the *SplitEnumerator*, and th
The [Source](https://github.com/apache/flink/blob/master/flink-core/src/main/java/org/apache/flink/api/connector/source/Source.java) class is API entry point that ties the above three components together.
-{{< img src="fig/source_components.svg" alt="Illustration of SplitEnumerator and SourceReader interacting" width="70%" >}}
+{{< img src="/fig/source_components.svg" alt="Illustration of SplitEnumerator and SourceReader interacting" width="70%" >}}
**Unified Across Streaming and Batch**
@@ -246,7 +246,7 @@ The `SplitFetcherManager` helps create and maintain a pool of `SplitFetcher`s ea
As an example, as illustrated below, a `SplitFetcherManager` may have a fixed number of threads, each fetching from some splits assigned to the `SourceReader`.
-{{< img width="70%" src="fig/source_reader.svg" alt="One fetcher per split threading model." >}}
+{{< img width="70%" src="/fig/source_reader.svg" alt="One fetcher per split threading model." >}}
The following code snippet implements this threading model.
@@ -378,7 +378,7 @@ Watermark Generators are only active during streaming execution. Batch execution
The data source API supports running watermark generators individually *per split*. That allows Flink to observe the event time progress per split individually, which is important to handle *event time skew* properly and prevent *idle partitions* from holding back the event time progress of the entire application.
-{{< img width="80%" src="fig/per_split_watermarks.svg" alt="Watermark Generation in a Source with two Splits." >}}
+{{< img width="80%" src="/fig/per_split_watermarks.svg" alt="Watermark Generation in a Source with two Splits." >}}
When implementing a source connector using the *Split Reader API*, this is automatically handled. All implementations based on the Split Reader API have split-aware watermarks out-of-the-box.