This is an automated email from the ASF dual-hosted git repository.
klion26 pushed a commit to branch release-1.12
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/release-1.12 by this push:
new 2e8d9b9 [FLINK-20384][doc] Fix Wrong Links in Some Chinese Docs
2e8d9b9 is described below
commit 2e8d9b9489a1ea33cecdcfc4d84912d5c68c1bf0
Author: huangxingbo <hxbks...@gmail.com>
AuthorDate: Fri Nov 27 10:31:15 2020 +0800
[FLINK-20384][doc] Fix Wrong Links in Some Chinese Docs
---
docs/deployment/filesystems/plugins.zh.md | 6 +++---
docs/deployment/ha/kubernetes_ha.zh.md | 6 +++---
docs/deployment/metric_reporters.zh.md | 4 ++--
docs/dev/python/table-api-users-guide/metrics.zh.md | 2 +-
docs/ops/metrics.zh.md | 2 +-
5 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/deployment/filesystems/plugins.zh.md
b/docs/deployment/filesystems/plugins.zh.md
index ff27e6d..ddcfbcf 100644
--- a/docs/deployment/filesystems/plugins.zh.md
+++ b/docs/deployment/filesystems/plugins.zh.md
@@ -70,7 +70,7 @@ possible across Flink core, plugins, and user code.
## File Systems
-All [file systems]({%link deployment/filesystems/index.md %}) **except MapR**
are pluggable. That means they can and should
+All [file systems]({%link deployment/filesystems/index.zh.md %}) **except
MapR** are pluggable. That means they can and should
be used as plugins. To use a pluggable file system, copy the corresponding JAR
file from the `opt`
directory to a directory under `plugins` directory of your Flink distribution
before starting Flink,
e.g.
@@ -116,7 +116,7 @@ Furthermore, loggers are whitelisted, so that they are
configured properly.
## Metric Reporters
-All [metric reporters]({% link deployment/metric_reporters.md %}) that Flink
provides can be used as plugins.
-See the [metrics]({% link ops/metrics.md %}) documentation for more details.
+All [metric reporters]({% link deployment/metric_reporters.zh.md %}) that
Flink provides can be used as plugins.
+See the [metrics]({% link ops/metrics.zh.md %}) documentation for more details.
{% top %}
diff --git a/docs/deployment/ha/kubernetes_ha.zh.md
b/docs/deployment/ha/kubernetes_ha.zh.md
index f2226ce..2618db6 100644
--- a/docs/deployment/ha/kubernetes_ha.zh.md
+++ b/docs/deployment/ha/kubernetes_ha.zh.md
@@ -24,7 +24,7 @@ under the License.
-->
## Kubernetes Cluster High Availability
-Kubernetes high availability service could support both [standalone Flink on
Kubernetes]({% link deployment/resource-providers/standalone/kubernetes.md %})
and [native Kubernetes integration]({% link
deployment/resource-providers/native_kubernetes.md %}).
+Kubernetes high availability service could support both [standalone Flink on
Kubernetes]({% link deployment/resource-providers/standalone/kubernetes.zh.md
%}) and [native Kubernetes integration]({% link
deployment/resource-providers/native_kubernetes.zh.md %}).
When running Flink JobManager as a Kubernetes deployment, the replica count
should be configured to 1 or greater.
* The value `1` means that a new JobManager will be launched to take over
leadership if the current one terminates exceptionally.
@@ -38,9 +38,9 @@ high-availability.storageDir: hdfs:///flink/recovery
{% endhighlight %}
#### Example: Highly Available Standalone Flink Cluster on Kubernetes
-Both session and job/application clusters support using the Kubernetes high
availability service. Users just need to add the following Flink config options
to [flink-configuration-configmap.yaml]({% link
deployment/resource-providers/standalone/kubernetes.md
%}#common-cluster-resource-definitions). All other yamls do not need to be
updated.
+Both session and job/application clusters support using the Kubernetes high
availability service. Users just need to add the following Flink config options
to [flink-configuration-configmap.yaml]({% link
deployment/resource-providers/standalone/kubernetes.zh.md
%}#common-cluster-resource-definitions). All other yamls do not need to be
updated.
-<span class="label label-info">Note</span> The filesystem which corresponds to
the scheme of your configured HA storage directory must be available to the
runtime. Refer to [custom Flink image]({% link
deployment/resource-providers/standalone/docker.md %}#customize-flink-image)
and [enable plugins]({% link deployment/resource-providers/standalone/docker.md
%}#using-plugins) for more information.
+<span class="label label-info">Note</span> The filesystem which corresponds to
the scheme of your configured HA storage directory must be available to the
runtime. Refer to [custom Flink image]({% link
deployment/resource-providers/standalone/docker.zh.md %}#customize-flink-image)
and [enable plugins]({% link
deployment/resource-providers/standalone/docker.zh.md %}#using-plugins) for
more information.
{% highlight yaml %}
apiVersion: v1
diff --git a/docs/deployment/metric_reporters.zh.md
b/docs/deployment/metric_reporters.zh.md
index 7ae05da..3a1fe0e 100644
--- a/docs/deployment/metric_reporters.zh.md
+++ b/docs/deployment/metric_reporters.zh.md
@@ -23,7 +23,7 @@ under the License.
-->
Flink allows reporting metrics to external systems.
-For more information about Flink's metric system go to the [metric system
documentation]({% link ops/metrics.md %}).
+For more information about Flink's metric system go to the [metric system
documentation]({% link ops/metrics.zh.md %}).
* This will be replaced by the TOC
{:toc}
@@ -61,7 +61,7 @@ metrics.reporter.my_other_reporter.port: 10000
{% endhighlight %}
**Important:** The jar containing the reporter must be accessible when Flink
is started. Reporters that support the
- `factory.class` property can be loaded as [plugins]({% link
deployment/filesystems/plugins.md %}). Otherwise the jar must be placed
+ `factory.class` property can be loaded as [plugins]({% link
deployment/filesystems/plugins.zh.md %}). Otherwise the jar must be placed
in the /lib folder. Reporters that are shipped with Flink (i.e., all
reporters documented on this page) are available
by default.
diff --git a/docs/dev/python/table-api-users-guide/metrics.zh.md
b/docs/dev/python/table-api-users-guide/metrics.zh.md
index d13914d..66faa1d 100644
--- a/docs/dev/python/table-api-users-guide/metrics.zh.md
+++ b/docs/dev/python/table-api-users-guide/metrics.zh.md
@@ -199,7 +199,7 @@ function_context
您可以参考Java的指标文档，以获取关于以下部分的更多详细信息：
-* [Reporter]({% link deployment/metric_reporters.md %}) 。
+* [Reporter]({% link deployment/metric_reporters.zh.md %}) 。
* [系统指标]({% link ops/metrics.zh.md %}#system-metrics) 。
* [延迟跟踪]({% link ops/metrics.zh.md %}#latency-tracking) 。
* [REST API集成]({% link ops/metrics.zh.md %}#rest-api-integration) 。
diff --git a/docs/ops/metrics.zh.md b/docs/ops/metrics.zh.md
index 9e01aeb..54dfb04 100644
--- a/docs/ops/metrics.zh.md
+++ b/docs/ops/metrics.zh.md
@@ -555,7 +555,7 @@ counter = getRuntimeContext()
## Reporter
-For information on how to set up Flink's metric reporters please take a look
at the [metric reporters documentation]({% link deployment/metric_reporters.md
%}).
+For information on how to set up Flink's metric reporters please take a look
at the [metric reporters documentation]({% link
deployment/metric_reporters.zh.md %}).
## System metrics
