You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by dw...@apache.org on 2021/11/05 07:56:21 UTC
[flink-web] branch asf-site updated (6dbfb0e -> de50d9e)
This is an automated email from the ASF dual-hosted git repository.
dwysakowicz pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git.
from 6dbfb0e Rebuild website
new 8091447 fix typos in Flink 1.14.0 release note
new de50d9e rebuild website
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
_posts/2021-09-29-release-1.14.0.md | 2 +-
content/blog/feed.xml | 2 +-
content/news/2021/09/29/release-1.14.0.html | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
[flink-web] 02/02: rebuild website
Posted by dw...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
dwysakowicz pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
commit de50d9e73a3713342381524d18f651b12261f793
Author: Yuan Mei <yu...@gmail.com>
AuthorDate: Fri Nov 5 13:16:24 2021 +0800
rebuild website
---
content/blog/feed.xml | 2 +-
content/news/2021/09/29/release-1.14.0.html | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 6934262..b3bbb83 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -718,7 +718,7 @@ produces a combined stream from multiple sources, by reading those sources one a
seamlessly switching over from one source to the other.</p>
<p>The motivating use case for the Hybrid Source was to read streams from tiered storage setups as if there was one
-stream that spans all tiers. For example, new data may land in Kafa and is eventually
+stream that spans all tiers. For example, new data may land in Kafka and is eventually
migrated to S3 (typically in compressed columnar format, for cost efficiency and performance).
The Hybrid Source can read this as one contiguous logical stream, starting with the historic data on S3
and transitioning over to the more recent data in Kafka.</p>
diff --git a/content/news/2021/09/29/release-1.14.0.html b/content/news/2021/09/29/release-1.14.0.html
index ba241c0..1cf2e9b 100644
--- a/content/news/2021/09/29/release-1.14.0.html
+++ b/content/news/2021/09/29/release-1.14.0.html
@@ -342,7 +342,7 @@ produces a combined stream from multiple sources, by reading those sources one a
seamlessly switching over from one source to the other.</p>
<p>The motivating use case for the Hybrid Source was to read streams from tiered storage setups as if there was one
-stream that spans all tiers. For example, new data may land in Kafa and is eventually
+stream that spans all tiers. For example, new data may land in Kafka and is eventually
migrated to S3 (typically in compressed columnar format, for cost efficiency and performance).
The Hybrid Source can read this as one contiguous logical stream, starting with the historic data on S3
and transitioning over to the more recent data in Kafka.</p>
[flink-web] 01/02: fix typos in Flink 1.14.0 release note
Posted by dw...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
dwysakowicz pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
commit 8091447e00222a12bf3576a64fe722104450031f
Author: Yuan Mei <yu...@gmail.com>
AuthorDate: Fri Nov 5 13:15:49 2021 +0800
fix typos in Flink 1.14.0 release note
---
_posts/2021-09-29-release-1.14.0.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_posts/2021-09-29-release-1.14.0.md b/_posts/2021-09-29-release-1.14.0.md
index 7e89577..14ceb36 100644
--- a/_posts/2021-09-29-release-1.14.0.md
+++ b/_posts/2021-09-29-release-1.14.0.md
@@ -123,7 +123,7 @@ produces a combined stream from multiple sources, by reading those sources one a
seamlessly switching over from one source to the other.
The motivating use case for the Hybrid Source was to read streams from tiered storage setups as if there was one
-stream that spans all tiers. For example, new data may land in Kafa and is eventually
+stream that spans all tiers. For example, new data may land in Kafka and is eventually
migrated to S3 (typically in compressed columnar format, for cost efficiency and performance).
The Hybrid Source can read this as one contiguous logical stream, starting with the historic data on S3
and transitioning over to the more recent data in Kafka.