This is an automated email from the ASF dual-hosted git repository.
dybyte pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/seatunnel.git
The following commit(s) were added to refs/heads/dev by this push:
new 59697b9bbc [Docs] Fix contributor guide dead links (#10875)
59697b9bbc is described below
commit 59697b9bbc90205a63c10dafc5ddc34e5d5c938f
Author: Daniel <[email protected]>
AuthorDate: Tue May 12 14:33:49 2026 +0800
[Docs] Fix contributor guide dead links (#10875)
---
docs/en/developer/contribute-plugin.md | 2 +-
docs/en/developer/contribute-transform-v2-guide.md | 4 ++--
docs/en/developer/how-to-create-your-connector.md | 2 +-
docs/en/faq.md | 8 ++++----
docs/zh/developer/contribute-plugin.md | 2 +-
docs/zh/developer/contribute-transform-v2-guide.md | 4 ++--
docs/zh/developer/how-to-create-your-connector.md | 3 +--
docs/zh/faq.md | 8 ++++----
8 files changed, 16 insertions(+), 17 deletions(-)
diff --git a/docs/en/developer/contribute-plugin.md
b/docs/en/developer/contribute-plugin.md
index ffd34ff705..91b6878d84 100644
--- a/docs/en/developer/contribute-plugin.md
+++ b/docs/en/developer/contribute-plugin.md
@@ -7,4 +7,4 @@ If you want to contribute Connector-V2, use the internal docs
below as the main
- [Source Connector Development](./source-connector-development.md)
- [Sink Connector Development](./sink-connector-development.md)
- [Set Up Develop Environment](./setup.md)
-- External repository guide: [Connector-v2 Contribution
Guide](https://github.com/apache/seatunnel/blob/dev/seatunnel-connectors-v2/README.md)
+- External repository guide: [Connector-v2 Contribution
Guide](../../../seatunnel-connectors-v2/README.md)
diff --git a/docs/en/developer/contribute-transform-v2-guide.md
b/docs/en/developer/contribute-transform-v2-guide.md
index 2fd4d767e2..f5cd3c8d8d 100644
--- a/docs/en/developer/contribute-transform-v2-guide.md
+++ b/docs/en/developer/contribute-transform-v2-guide.md
@@ -50,10 +50,10 @@ Transforms are easier to review when the code, docs, and
examples change togethe
2. [Transforms Catalog](../transforms)
3. [Transform Common Options](../transforms/common-options/common-options.md)
4. [Core API Design](../architecture/core-api-design.md)
-5. [seatunnel-transforms-v2
README](https://github.com/apache/seatunnel/blob/dev/seatunnel-transforms-v2/README.md)
+5. [seatunnel-transforms-v2 README](../../../seatunnel-transforms-v2/README.md)
## When You Need The Repository-Level Guide
For module-specific details such as transform module conventions or examples
inside the `seatunnel-transforms-v2` tree, continue with the repository guide:
-- [Transform-V2 Contribution
Guide](https://github.com/apache/seatunnel/blob/dev/seatunnel-transforms-v2/README.md)
+- [Transform-V2 Contribution Guide](../../../seatunnel-transforms-v2/README.md)
diff --git a/docs/en/developer/how-to-create-your-connector.md
b/docs/en/developer/how-to-create-your-connector.md
index 38d59f5cae..19693ed931 100644
--- a/docs/en/developer/how-to-create-your-connector.md
+++ b/docs/en/developer/how-to-create-your-connector.md
@@ -1,6 +1,6 @@
# Develop Your Own Connector
-If you want to develop your own connector for the new SeaTunnel connector API
(Connector V2), please check
[here](https://github.com/apache/seatunnel/blob/dev/seatunnel-connectors-v2/README.md).
+If you want to develop your own connector for the new SeaTunnel connector API
(Connector V2), please check [here](../../../seatunnel-connectors-v2/README.md).
## Start Here
diff --git a/docs/en/faq.md b/docs/en/faq.md
index 4b06bcb97b..4000e8c268 100644
--- a/docs/en/faq.md
+++ b/docs/en/faq.md
@@ -10,8 +10,8 @@ Use these entry points first:
## What data sources and destinations does SeaTunnel support?
SeaTunnel supports various data sources and destinations. You can find a
detailed list on the following list:
-- Supported data sources (Source): [Source List](../connectors/source)
-- Supported data destinations (Sink): [Sink List](../connectors/sink)
+- Supported data sources (Source): [Source List](./connectors/source)
+- Supported data destinations (Sink): [Sink List](./connectors/sink)
## Does SeaTunnel support batch and streaming processing?
SeaTunnel supports both batch and streaming processing modes. You can select
the appropriate mode based on your specific business scenarios and needs. Batch
processing is suitable for scheduled data integration tasks, while streaming
processing is ideal for real-time integration and Change Data Capture (CDC).
@@ -29,7 +29,7 @@ Yes, SeaTunnel supports custom data cleansing rules. You can
configure custom ru
SeaTunnel supports incremental data integration. For example, the CDC
connector allows real-time capture of data changes, which is ideal for
scenarios requiring real-time data integration.
## What CDC data sources are currently supported by SeaTunnel?
-SeaTunnel currently supports MongoDB CDC, MySQL CDC, OpenGauss CDC, Oracle
CDC, PostgreSQL CDC, SQL Server CDC, TiDB CDC, and more. For more details,
refer to the [Source List](../connectors/source).
+SeaTunnel currently supports MongoDB CDC, MySQL CDC, OpenGauss CDC, Oracle
CDC, PostgreSQL CDC, SQL Server CDC, TiDB CDC, and more. For more details,
refer to the [Source List](./connectors/source).
## How do I enable permissions required for SeaTunnel CDC integration?
Please refer to the official SeaTunnel documentation for the necessary steps
to enable permissions for each connector’s CDC functionality.
@@ -123,4 +123,4 @@ For more details, see:
[lightbend/config#456](https://github.com/lightbend/confi
SeaTunnel features a highly abstracted and well-structured architecture,
making it an excellent choice for learning big data architecture. You can start
by exploring and debugging the `seatunnel-examples` module:
`SeaTunnelEngineLocalExample.java`. For more details, refer to the [SeaTunnel
Contribution Guide](https://seatunnel.apache.org/docs/developer/setup).
## Do I need to understand all of SeaTunnel’s source code if I want to develop
my own source, sink, or transform?
-No, you only need to focus on the interfaces for source, sink, and transform.
If you want to develop your own connector (Connector V2) for the SeaTunnel API,
refer to the **[Connector Development
Guide](https://github.com/apache/seatunnel/blob/dev/seatunnel-connectors-v2/README.md)**.
+No, you only need to focus on the interfaces for source, sink, and transform.
If you want to develop your own connector (Connector V2) for the SeaTunnel API,
refer to the **[Connector Development
Guide](../../seatunnel-connectors-v2/README.md)**.
diff --git a/docs/zh/developer/contribute-plugin.md
b/docs/zh/developer/contribute-plugin.md
index 10ebeff79f..700183284c 100644
--- a/docs/zh/developer/contribute-plugin.md
+++ b/docs/zh/developer/contribute-plugin.md
@@ -7,4 +7,4 @@
- [Source Connector 开发指南](./source-connector-development.md)
- [Sink Connector 开发指南](./sink-connector-development.md)
- [搭建开发环境](./setup.md)
-- 外部仓库指南：[Connector-v2
贡献指南](https://github.com/apache/seatunnel/blob/dev/seatunnel-connectors-v2/README.zh.md)
+- 外部仓库指南：[Connector-v2 贡献指南](../../../seatunnel-connectors-v2/README.zh.md)
diff --git a/docs/zh/developer/contribute-transform-v2-guide.md
b/docs/zh/developer/contribute-transform-v2-guide.md
index c9ef272294..6647521fb3 100644
--- a/docs/zh/developer/contribute-transform-v2-guide.md
+++ b/docs/zh/developer/contribute-transform-v2-guide.md
@@ -50,10 +50,10 @@ Transform 类改动如果能同时带上代码、文档和示例，通常更容
2. [Transforms 目录](../transforms)
3. [Transform 通用参数](../transforms/common-options/common-options.md)
4. [核心 API 设计](../architecture/core-api-design.md)
-5. [seatunnel-transforms-v2
README](https://github.com/apache/seatunnel/blob/dev/seatunnel-transforms-v2/README.zh.md)
+5. [seatunnel-transforms-v2
README](../../../seatunnel-transforms-v2/README.zh.md)
## 什么时候继续看仓库级指南
如果你需要的是 `seatunnel-transforms-v2` 模块内部的约定、示例或更贴近源码目录的说明，再继续看仓库里的指南：
-- [Transform-V2
贡献指南](https://github.com/apache/seatunnel/blob/dev/seatunnel-transforms-v2/README.zh.md)
+- [Transform-V2 贡献指南](../../../seatunnel-transforms-v2/README.zh.md)
diff --git a/docs/zh/developer/how-to-create-your-connector.md
b/docs/zh/developer/how-to-create-your-connector.md
index 0d9247e475..17ee348330 100644
--- a/docs/zh/developer/how-to-create-your-connector.md
+++ b/docs/zh/developer/how-to-create-your-connector.md
@@ -1,6 +1,6 @@
# 开发自己的Connector
-如果你想针对SeaTunnel新的连接器API开发自己的连接器（Connector
V2），请查看[这里](https://github.com/apache/seatunnel/blob/dev/seatunnel-connectors-v2/README.zh.md)
。
+如果你想针对SeaTunnel新的连接器API开发自己的连接器（Connector
V2），请查看[这里](../../../seatunnel-connectors-v2/README.zh.md) 。
## 从这里开始
@@ -23,4 +23,3 @@
- [检查点机制](../architecture/fault-tolerance/checkpoint-mechanism.md) - 容错和状态管理
这些文档将帮助你理解 SeaTunnel 连接器中使用的底层架构和设计模式。
-
diff --git a/docs/zh/faq.md b/docs/zh/faq.md
index aada1b92bc..7fbcc8208f 100644
--- a/docs/zh/faq.md
+++ b/docs/zh/faq.md
@@ -10,8 +10,8 @@
## SeaTunnel 支持哪些数据来源和数据目的地？
SeaTunnel 支持多种数据源来源和数据目的地，您可以在官网找到详细的列表：
-SeaTunnel 支持的数据来源(Source)列表：[Source List](../connectors/source)
-SeaTunnel 支持的数据目的地(Sink)列表：[Sink List](../connectors/sink)
+SeaTunnel 支持的数据来源(Source)列表：[Source List](./connectors/source)
+SeaTunnel 支持的数据目的地(Sink)列表：[Sink List](./connectors/sink)
## SeaTunnel 是否支持批处理和流处理？
SeaTunnel 支持批流一体，SeaTunnel
可以设置批处理和流处理两种模式。您可以根据具体的业务场景和需求选择合适的处理模式。批处理适合定时数据同步场景，而流处理适合实时同步和数据变更捕获 (CDC)
场景。
@@ -30,7 +30,7 @@ SeaTunnel 支持自定义数据清洗规则。可以在 `transform` 模块中配
SeaTunnel 支持增量数据同步。例如通过 CDC 连接器实现对数据库的增量同步，适用于需要实时捕获数据变更的场景。
## SeaTunnel 目前支持哪些数据源的 CDC ？
-目前支持 MongoDB CDC、MySQL CDC、Opengauss CDC、Oracle CDC、PostgreSQL CDC、Sql Server
CDC、TiDB CDC等，更多请查阅[Source](../connectors/source)。
+目前支持 MongoDB CDC、MySQL CDC、Opengauss CDC、Oracle CDC、PostgreSQL CDC、Sql Server
CDC、TiDB CDC等，更多请查阅[Source](./connectors/source)。
## SeaTunnel CDC 同步需要的权限如何开启？
这样就可以了。
@@ -131,4 +131,4 @@ SeaTunnel 拥有完全抽象、结构化的非常优秀的架构设计和代码
## 如果想开发自己的 source、sink、transform 时，是否需要了解 SeaTunnel 所有源代码？
不需要，您只需要关注 source、sink、transform 对应的接口即可。
-如果你想针对 SeaTunnel API 开发自己的连接器（Connector V2），请查看**[Connector Development
Guide](https://github.com/apache/seatunnel/blob/dev/seatunnel-connectors-v2/README.zh.md)**
。
+如果你想针对 SeaTunnel API 开发自己的连接器（Connector V2），请查看**[Connector Development
Guide](../../seatunnel-connectors-v2/README.zh.md)** 。
