This is an automated email from the ASF dual-hosted git repository.
martijnvisser 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 358c1e47a87 [hotfix][docs-zh] Add known issues with Pulsar client
under Java 11 to Chinese documentation.
358c1e47a87 is described below
commit 358c1e47a87a32b4c67c8cdedb5273300162ff49
Author: zhuanshenbsj1 <[email protected]>
AuthorDate: Tue Apr 19 00:00:47 2022 +0800
[hotfix][docs-zh] Add known issues with Pulsar client under Java 11 to
Chinese documentation.
---
.../docs/connectors/datastream/pulsar.md | 13 +++++++++
docs/content/docs/connectors/datastream/pulsar.md | 34 +++++++++++-----------
2 files changed, 30 insertions(+), 17 deletions(-)
diff --git a/docs/content.zh/docs/connectors/datastream/pulsar.md
b/docs/content.zh/docs/connectors/datastream/pulsar.md
index 8d44be88c71..cfba3cb1530 100644
--- a/docs/content.zh/docs/connectors/datastream/pulsar.md
+++ b/docs/content.zh/docs/connectors/datastream/pulsar.md
@@ -650,7 +650,20 @@ Pulsar Sink 遵循
[FLIP-191](https://cwiki.apache.org/confluence/display/FLINK/
用户遇到的问题可能与 Flink 无关，请先升级 Pulsar 的版本、Pulsar 客户端的版本，或者修改 Pulsar 的配置、Pulsar
连接器的配置来尝试解决问题。
+## 已知问题
+
+本节介绍有关 Pulsar 连接器的一些已知问题。
+
### 在 Java 11 上使用不稳定
Pulsar connector 在 Java 11 中有一些尚未修复的问题。我们当前推荐在 Java 8 环境中运行Pulsar connector.
+
+### 不自动重连，而是抛出TransactionCoordinatorNotFound异常
+
+Pulsar 事务机制仍在积极发展中，当前版本并不稳定。 Pulsar 2.9.2
+引入了这个问题 [a break change](https://github.com/apache/pulsar/pull/13135)。
+如果您使用 Pulsar 2.9.2或更高版本与较旧的 Pulsar
客户端一起使用，您可能会收到一个“TransactionCoordinatorNotFound”异常。
+
+您可以使用最新的`pulsar-client-all`分支来解决这个问题。
+
{{< top >}}
diff --git a/docs/content/docs/connectors/datastream/pulsar.md
b/docs/content/docs/connectors/datastream/pulsar.md
index 0953753ee33..4d30907a306 100644
--- a/docs/content/docs/connectors/datastream/pulsar.md
+++ b/docs/content/docs/connectors/datastream/pulsar.md
@@ -768,23 +768,6 @@ you to reuse the same Flink job after certain "allowed"
data model changes, like
a field in a AVRO-based Pojo class. Please note that you can specify Pulsar
schema validation rules
and define an auto schema update. For details, refer to [Pulsar Schema
Evolution](https://pulsar.apache.org/docs/en/schema-evolution-compatibility/).
-## Known Issues
-
-This section describes some known issues about the Pulsar connectors.
-
-### Unstable on Java 11
-
-Pulsar connector has some known issues on Java 11. It is recommended to run
Pulsar connector
-on Java 8.
-
-### No TransactionCoordinatorNotFound, but automatic reconnect
-
-Pulsar transactions are still in active development and are not stable. Pulsar
2.9.2
-introduces [a break change](https://github.com/apache/pulsar/pull/13135) in
transactions.
-If you use Pulsar 2.9.2 or higher with an older Pulsar client, you might get a
`TransactionCoordinatorNotFound` exception.
-
-You can use the latest `pulsar-client-all` release to resolve this issue.
-
## Upgrading to the Latest Connector Version
The generic upgrade steps are outlined in [upgrading jobs and Flink versions
guide]({{< ref "docs/ops/upgrading" >}}).
@@ -802,4 +785,21 @@ If you have a problem with Pulsar when using Flink, keep
in mind that Flink only
and your problem might be independent of Flink and sometimes can be solved by
upgrading Pulsar brokers,
reconfiguring Pulsar brokers or reconfiguring Pulsar connector in Flink.
+## Known Issues
+
+This section describes some known issues about the Pulsar connectors.
+
+### Unstable on Java 11
+
+Pulsar connector has some known issues on Java 11. It is recommended to run
Pulsar connector
+on Java 8.
+
+### No TransactionCoordinatorNotFound, but automatic reconnect
+
+Pulsar transactions are still in active development and are not stable. Pulsar
2.9.2
+introduces [a break change](https://github.com/apache/pulsar/pull/13135) in
transactions.
+If you use Pulsar 2.9.2 or higher with an older Pulsar client, you might get a
`TransactionCoordinatorNotFound` exception.
+
+You can use the latest `pulsar-client-all` release to resolve this issue.
+
{{< top >}}
