This is an automated email from the ASF dual-hosted git repository.
jianglongtao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new 4f886ecaa13 Patch invalidlink (#29864)
4f886ecaa13 is described below
commit 4f886ecaa1386c5ae8c53cd25d35e5e8d68ad76a
Author: ray.zh <[email protected]>
AuthorDate: Fri Jan 26 10:35:20 2024 +0800
Patch invalidlink (#29864)
* Update _index.cn.md
fix invalid link
* Update _index.en.md
fix invalid link
---
.../yaml-config/jdbc-driver/known-implementation/_index.cn.md | 4 ++--
.../yaml-config/jdbc-driver/known-implementation/_index.en.md | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.cn.md
b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.cn.md
index 8b0caf285fc..6040b0e45b2 100644
---
a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.cn.md
+++
b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.cn.md
@@ -11,11 +11,11 @@ chapter = true
可允许从多种来源和 File System 获取并解析为 ShardingSphere 的 YAML 配置文件。
在解析并加载 YAML 文件为 ShardingSphere 的元数据后，
-会再次通过[模式配置](../../../java-api/mode.cn.md)的相关配置决定下一步行为。讨论两种情况：
+会再次通过[模式配置](../../../java-api/mode)的相关配置决定下一步行为。讨论两种情况：
1. 元数据持久化仓库中不存在 ShardingSphere 的元数据，本地元数据将被存储到元数据持久化仓库。
2. 元数据持久化仓库中已存在与本地元数据不同的 ShardingSphere 的元数据，本地元数据将被元数据持久化仓库的元数据覆盖。
-对元数据持久化仓库的配置需参考[元数据持久化仓库](../../../../common-config/builtin-algorithm/metadata-repository.cn.md)。
+对元数据持久化仓库的配置需参考[元数据持久化仓库](../../../../common-config/builtin-algorithm/metadata-repository)。
## URL 配置
diff --git
a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.en.md
b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.en.md
index 9a50599bae5..a78f2579e2d 100644
---
a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.en.md
+++
b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.en.md
@@ -11,11 +11,11 @@ by implementing the SPI of
`org.apache.shardingsphere.driver.jdbc.core.driver.Sh
allows YAML configuration files to be fetched from multiple sources and File
Systems and parsed into ShardingSphere.
After parsing and loading the YAML file into ShardingSphere's metadata,
-The next behavior will be determined again through the relevant configuration
of [Mode Configuration](../../../java-api/mode.cn.md). Discuss two situations:
+The next behavior will be determined again through the relevant configuration
of [Mode Configuration](../../../java-api/mode). Discuss two situations:
1. ShardingSphere’s metadata does not exist in the metadata persistence
warehouse, and local metadata will be stored in the metadata persistence
warehouse.
2. Metadata of ShardingSphere that is different from local metadata already
exists in the metadata persistence warehouse, and the local metadata will be
overwritten by the metadata of the metadata persistence warehouse.
-For the configuration of the metadata persistence warehouse, please refer to
[Metadata Persistence
Warehouse](../../../../common-config/builtin-algorithm/metadata-repository.cn.md).
+For the configuration of the metadata persistence warehouse, please refer to
[Metadata Persistence
Warehouse](../../../../common-config/builtin-algorithm/metadata-repository).
## URL configuration
