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 87624ab [hotfix][docs] Fix typos
87624ab is described below
commit 87624ab10d1e417c6dff8d24403374e5e76e0e3e
Author: LightGHLi <[email protected]>
AuthorDate: Fri Jul 23 16:31:36 2021 +0800
[hotfix][docs] Fix typos
---
docs/content.zh/docs/connectors/datastream/overview.md | 2 +-
docs/content.zh/docs/dev/python/table/python_table_api_connectors.md | 2 +-
docs/content.zh/release-notes/flink-1.8.md | 2 +-
docs/content.zh/release-notes/flink-1.9.md | 2 +-
docs/content/docs/dev/python/table/python_table_api_connectors.md | 2 +-
docs/content/release-notes/flink-1.8.md | 2 +-
docs/content/release-notes/flink-1.9.md | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/content.zh/docs/connectors/datastream/overview.md
b/docs/content.zh/docs/connectors/datastream/overview.md
index 889f38f..5a580d9 100644
--- a/docs/content.zh/docs/connectors/datastream/overview.md
+++ b/docs/content.zh/docs/connectors/datastream/overview.md
@@ -63,7 +63,7 @@ Flink 还有些一些额外的连接器通过 [Apache Bahir](https://bahir.apach
* [Akka](https://bahir.apache.org/docs/flink/current/flink-streaming-akka/)
(sink)
* [Netty](https://bahir.apache.org/docs/flink/current/flink-streaming-netty/)
(source)
-## 连接Fink的其他方法
+## 连接Flink的其他方法
### 异步 I/O
diff --git
a/docs/content.zh/docs/dev/python/table/python_table_api_connectors.md
b/docs/content.zh/docs/dev/python/table/python_table_api_connectors.md
index c672932..8f786b5 100644
--- a/docs/content.zh/docs/dev/python/table/python_table_api_connectors.md
+++ b/docs/content.zh/docs/dev/python/table/python_table_api_connectors.md
@@ -41,7 +41,7 @@
table_env.get_config().get_configuration().set_string("pipeline.jars", "file:///
## 如何使用连接器
-在 PyFink Table API 中，DDL 是定义 source 和 sink 比较推荐的方式，这可以通过
+在 PyFlink Table API 中，DDL 是定义 source 和 sink 比较推荐的方式，这可以通过
`TableEnvironment` 中的 `execute_sql()` 方法来完成，然后就可以在作业中使用这张表了。
```python
diff --git a/docs/content.zh/release-notes/flink-1.8.md
b/docs/content.zh/release-notes/flink-1.8.md
index baf28c4..5e263a3 100644
--- a/docs/content.zh/release-notes/flink-1.8.md
+++ b/docs/content.zh/release-notes/flink-1.8.md
@@ -206,7 +206,7 @@ for instructions on using `CompositeTypeSerializerSnapshot`.
### Memory management
-In Fink 1.8.0 and prior version, the managed memory fraction of taskmanager is
controlled by `taskmanager.memory.fraction`,
+In Flink 1.8.0 and prior version, the managed memory fraction of taskmanager
is controlled by `taskmanager.memory.fraction`,
and with 0.7 as the default value. However, sometimes this will cause OOMs due
to the fact that the default value of JVM
parameter `NewRatio` is 2, which means the old generation occupied only 2/3
(0.66) of the heap memory. So if you run into
this case, please manually change this value to a lower value.
diff --git a/docs/content.zh/release-notes/flink-1.9.md
b/docs/content.zh/release-notes/flink-1.9.md
index 67dd7c4..f0e49d9 100644
--- a/docs/content.zh/release-notes/flink-1.9.md
+++ b/docs/content.zh/release-notes/flink-1.9.md
@@ -78,7 +78,7 @@ Related issues:
### Memory management
-In Fink 1.9.0 and prior version, the managed memory fraction of taskmanager is
controlled by `taskmanager.memory.fraction`,
+In Flink 1.9.0 and prior version, the managed memory fraction of taskmanager
is controlled by `taskmanager.memory.fraction`,
and with 0.7 as the default value. However, sometimes this will cause OOMs due
to the fact that the default value of JVM
parameter `NewRatio` is 2, which means the old generation occupied only 2/3
(0.66) of the heap memory. So if you run into
this case, please manually change this value to a lower value.
diff --git a/docs/content/docs/dev/python/table/python_table_api_connectors.md
b/docs/content/docs/dev/python/table/python_table_api_connectors.md
index 51f8f4d..6b3743a 100644
--- a/docs/content/docs/dev/python/table/python_table_api_connectors.md
+++ b/docs/content/docs/dev/python/table/python_table_api_connectors.md
@@ -43,7 +43,7 @@
table_env.get_config().get_configuration().set_string("pipeline.jars", "file:///
## How to use connectors
-In PyFink's Table API, DDL is the recommended way to define sources and sinks,
executed via the
+In PyFlink's Table API, DDL is the recommended way to define sources and
sinks, executed via the
`execute_sql()` method on the `TableEnvironment`.
This makes the table available for use by the application.
diff --git a/docs/content/release-notes/flink-1.8.md
b/docs/content/release-notes/flink-1.8.md
index baf28c4..5e263a3 100644
--- a/docs/content/release-notes/flink-1.8.md
+++ b/docs/content/release-notes/flink-1.8.md
@@ -206,7 +206,7 @@ for instructions on using `CompositeTypeSerializerSnapshot`.
### Memory management
-In Fink 1.8.0 and prior version, the managed memory fraction of taskmanager is
controlled by `taskmanager.memory.fraction`,
+In Flink 1.8.0 and prior version, the managed memory fraction of taskmanager
is controlled by `taskmanager.memory.fraction`,
and with 0.7 as the default value. However, sometimes this will cause OOMs due
to the fact that the default value of JVM
parameter `NewRatio` is 2, which means the old generation occupied only 2/3
(0.66) of the heap memory. So if you run into
this case, please manually change this value to a lower value.
diff --git a/docs/content/release-notes/flink-1.9.md
b/docs/content/release-notes/flink-1.9.md
index 67dd7c4..f0e49d9 100644
--- a/docs/content/release-notes/flink-1.9.md
+++ b/docs/content/release-notes/flink-1.9.md
@@ -78,7 +78,7 @@ Related issues:
### Memory management
-In Fink 1.9.0 and prior version, the managed memory fraction of taskmanager is
controlled by `taskmanager.memory.fraction`,
+In Flink 1.9.0 and prior version, the managed memory fraction of taskmanager
is controlled by `taskmanager.memory.fraction`,
and with 0.7 as the default value. However, sometimes this will cause OOMs due
to the fact that the default value of JVM
parameter `NewRatio` is 2, which means the old generation occupied only 2/3
(0.66) of the heap memory. So if you run into
this case, please manually change this value to a lower value.
