apache · dataroaring · Jun 10, 2026
diff --git a/.github/workflows/build-check.yml b/.github/workflows/build-check.yml
@@ -239,14 +239,8 @@ jobs:
                   rm -rf build
 
             - name: Docs changed link gate
-              continue-on-error: true
               run: |
-                  # Report-only: the bulk-rename in the new-homepage launch PR
-                  # exposes ~30 latent anchor/link issues that pre-date this
-                  # change. They're being chipped away in follow-up PRs and
-                  # should not block the launch. The full findings still write
-                  # to the report file below for audit.
-                  yarn docs:links:changed --output website-quality-governance/generated/docs-links-report.json
+                  yarn docs:links:changed --fail-on-errors --output website-quality-governance/generated/docs-links-report.json
 
             - name: Docs governance report
               if: always()

diff --git a/blog/Annoucing.md b/blog/Annoucing.md
@@ -41,16 +41,16 @@

 **Apache Doris GitHub:**

 [https://github.com/apache/doris](https://github.com/apache/doris)

 **Apache Doris website:**

 [http://doris.apache.org](http://doris.apache.org)
 
 **Please contact us via:**
 
-[dev@doris.apache.org.](dev@doris.apache.org.)
+[dev@doris.apache.org](mailto:dev@doris.apache.org)
 
 **See How to subscribe:**
 
 [https://doris.apache.org/community/subscribe-mail-list](https://doris.apache.org/community/subscribe-mail-list/)
diff --git a/blog/release-note-1.1.0.md b/blog/release-note-1.1.0.md
@@ -31,13 +31,13 @@

 In order to ensure the maintainability of the code structure and reduce the additional learning and development costs caused by redundant historical codes, we have decided to no longer support the Segment v1 storage format from the next version. It is expected that this part of the code will be deleted in the Apache Doris 1.2 version, and all users who are still using the Segment V1 storage format must complete the data format conversion in version 1.1. Please refer to the following link for the operation manual:

 [https://doris.apache.org/zh-CN/docs/1.0/administrator-guide/segment-v2-usage](https://doris.apache.org/zh-CN/docs/1.0/administrator-guide/segment-v2-usage)

 ### Normal Upgrade

 For normal upgrade operations, you can perform rolling upgrades according to the cluster upgrade documentation on the official website.

 [https://doris.apache.org/zh-CN/docs/admin-manual/cluster-management/upgrade](https://doris.apache.org/zh-CN/docs/admin-manual/cluster-management/upgrade)

 ## Features

@@ -87,9 +87,9 @@

 **Performance test report**

 [https://doris.apache.org/zh-CN/docs/benchmark/ssb](https://doris.apache.org/zh-CN/docs/benchmark/ssb)

 [https://doris.apache.org/zh-CN/docs/benchmark/tpch](https://doris.apache.org/zh-CN/docs/benchmark/tpch)

 ### Compaction logic optimization and real-time guarantee

@@ -169,15 +169,15 @@

 ### Download Link

 [hhttps://doris.apache.org/download](https://doris.apache.org/download)

 ### Feedback

 If you encounter any problems with use, please feel free to contact us through GitHub discussion forum or Dev e-mail group anytime.
 
 GitHub Forum: [https://github.com/apache/doris/discussions](https://github.com/apache/doris/discussions)
 
-Mailing list: [dev@doris.apache.org](dev@doris.apache.org)
+Mailing list: [dev@doris.apache.org](mailto:dev@doris.apache.org)
 
 ## Thanks
 

diff --git a/blog/release-note-2.1.6.md b/blog/release-note-2.1.6.md
@@ -36,7 +36,7 @@

 ## Behavior changes

 - Removed the `delete_if_exists` option from create repository. [#38192](https://github.com/apache/doris/pull/38192)

 - Added the `enable_prepared_stmt_audit_log` session variable to control whether JDBC prepared statements record audit logs, with the default being no recording. [#38624](https://github.com/apache/doris/pull/38624) [#39009](https://github.com/apache/doris/pull/39009)

@@ -525,4 +525,4 @@
 
 For example, if you are upgrading from version 0.15.x to 2.0.x, it is recommended to first upgrade to the latest version of 1.1, then upgrade to the latest version of 1.2, and finally upgrade to the latest version of 2.0.
 
-For more upgrade information, see the documentation: [Cluster Upgrade](../../admin-manual/cluster-management/upgrade)
+For more upgrade information, see the documentation: [Cluster Upgrade](../versioned_docs/version-2.1/admin-manual/cluster-management/upgrade.md)
diff --git a/blog/ssb.md b/blog/ssb.md
@@ -133,7 +133,7 @@ Here we use Apache Doris 1.2.0-rc01, Apache Doris 1.1.3 and Apache Doris 0.15.0
 
 ## 6. Environment Preparation
 
-Please first refer to the [official documentation](../install/deploy-manually/storage-compute-decoupled-deploy-manually) to install and deploy Apache Doris first to obtain a Doris cluster which is working well(including at least 1 FE 1 BE, 1 FE 3 BEs is recommended).
+Please first refer to the [official documentation](../docs/install/deploy-manually/separating-storage-compute-deploy-manually.md) to install and deploy Apache Doris first to obtain a Doris cluster which is working well(including at least 1 FE 1 BE, 1 FE 3 BEs is recommended).
 
 The scripts mentioned in the following documents are stored in the Apache Doris codebase: [ssb-tools](https://github.com/apache/doris/tree/master/tools/ssb-tools)
 

diff --git a/docs/admin-manual/auth/integrations/aws-iam-role.md b/docs/admin-manual/auth/integrations/aws-iam-role.md
@@ -156,4 +156,4 @@ Key parameters:
 | `s3.external_id` | No | The externalId value configured in the Trust Relationships Policies |
 | `timeout` | No | Operation timeout, in seconds |
 
-For detailed usage of SQL statements for more features, see [AWS Authentication and Authorization](../../../admin-manual/auth/integrations/aws-authentication-and-authorization#assumed-role-authentication).
+For detailed usage of SQL statements for more features, see [AWS Authentication and Authorization](../../../admin-manual/auth/integrations/aws-authentication-and-authorization#assumed-role-authentication-and-authorization).
diff --git a/...ual/trouble-shooting/memory-management/memory-analysis/query-memory-analysis.md b/...ual/trouble-shooting/memory-management/memory-analysis/query-memory-analysis.md
@@ -26,7 +26,7 @@ The memory statistics of historical queries can be viewed in `peakMemoryBytes` o
 
 ## Use Query Profile to analyze query memory usage
 
-Find query information including SQL in `fe/log/fe.audit.log` based on QueryID, get the query plan by `explain SQL`, and get the query profile by executing SQL after `set enable_profile=true`. For a detailed introduction to Query Profile, refer to the document [Query Profile](../../../../query-acceleration/performance-tuning-overview/analysis-tools#doris-profile). Here we only introduce the memory-related content in Query Profile, and locate the Operator and data structure that use a lot of memory based on it.
+Find query information including SQL in `fe/log/fe.audit.log` based on QueryID, get the query plan by `explain SQL`, and get the query profile by executing SQL after `set enable_profile=true`. For a detailed introduction to Query Profile, refer to the document [Query Profile](../../../../query-acceleration/performance-tuning-overview/analysis-tools#doris-profile-analyzing-execution-layer-bottlenecks). Here we only introduce the memory-related content in Query Profile, and locate the Operator and data structure that use a lot of memory based on it.
 
 1. Locate Operators or memory data structures that use a lot of memory
 

diff --git a/docs/ai/ai-overview.md b/docs/ai/ai-overview.md
@@ -30,7 +30,7 @@ The following table lists common AI scenarios and the corresponding capabilities
 | Let AI Agents query business data in real time | [Agent Facing Analytics](#agent-facing-analytics) | MPP architecture, millisecond-level queries, MCP Server |
 | Run keyword search, vector search, and aggregation on the same data | [Hybrid search and analytics](#hybrid-search-and-analytics-processing) | Inverted index + vector index + SQL |
 | Accelerate AI training data preparation and feature engineering | [Lakehouse for AI](#lakehouse-for-ai) | Lakehouse architecture, open table formats, fast SQL |
-| Build enterprise knowledge bases and intelligent customer service | [RAG applications](#ragretrieval-augmented-generation) | High-concurrency vector retrieval, hybrid search |
+| Build enterprise knowledge bases and intelligent customer service | [RAG applications](#rag-retrieval-augmented-generation) | High-concurrency vector retrieval, hybrid search |
 | Monitor model training and inference services | [AI Observability](#ai-observability) | High-throughput ingestion, inverted index, low storage cost |
 | Make search understand user intent | [Semantic search](#semantic-search) | HNSW/IVF, quantization, multimodal extensions |
 

diff --git a/docs/compute-storage-decoupled/file-cache/file-cache.md b/docs/compute-storage-decoupled/file-cache/file-cache.md
@@ -305,7 +305,7 @@ Cache-related metrics in the SQL Profile are located under the `SegmentIterator`
 | `RemoteIOUseTimer` | Time spent reading from remote storage |
 | `WriteCacheIOUseTimer` | Time spent writing into the file cache |
 
-You can view the complete query performance report through [Query Performance Analysis](../../query-acceleration/performance-tuning-overview/analysis-tools#doris-profile).
+You can view the complete query performance report through [Query Performance Analysis](../../query-acceleration/performance-tuning-overview/analysis-tools#doris-profile-analyzing-execution-layer-bottlenecks).
 
 ## TTL Cache Policy
 

diff --git a/docs/connection-integration/data-integration/flink-doris-connector.md b/docs/connection-integration/data-integration/flink-doris-connector.md
@@ -819,7 +819,7 @@ After the Flink cluster is started, you can run the corresponding command accord
 | sink.label-prefix           | --            | Y        | The label prefix used for Stream Load imports. In 2pc scenarios, it must be globally unique to guarantee the EOS semantics of Flink.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | sink.properties.*           | --            | N        | Stream Load import parameters. For example: `'sink.properties.column_separator' = ', '` defines the column separator; `'sink.properties.escape_delimiters' = 'true'` indicates that special characters are used as separators, and `\x01` will be converted to the binary `0x01`; for JSON-format imports: `'sink.properties.format' = 'json'`, `'sink.properties.read_json_by_line' = 'true'`. For detailed parameters, see [Stream Load](../../data-operate/import/import-way/stream-load-manual.md#import-configuration-parameters). Group Commit mode: `'sink.properties.group_commit' = 'sync_mode'` sets group commit to synchronous mode. Flink Connector supports configuring group commit for imports starting from 1.6.2. For detailed usage and limitations, see [Group Commit](../../data-operate/import/load-best-practices/group-commit-manual.md). Since 26.1.0, gz compression is enabled by default for Stream Load; it can be disabled by setting `'sink.properties.compress_type' = ''`. |
 | sink.enable-delete          | TRUE          | N        | Whether to enable deletion. This option requires the Doris table to have batch deletion enabled (enabled by default in Doris 0.15+) and only supports the Unique model.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| sink.enable-2pc             | TRUE          | N        | Whether to enable two-phase commit (2pc). The default is true, which guarantees Exactly-Once semantics. For information on two-phase commit, see [Stream Load 2PC](../../data-operate/transaction.md#streamload-2pc).                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| sink.enable-2pc             | TRUE          | N        | Whether to enable two-phase commit (2pc). The default is true, which guarantees Exactly-Once semantics. For information on two-phase commit, see [Stream Load 2PC](../../data-operate/transaction.md#stream-load-2pc).                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | sink.buffer-size            | 1MB           | N        | Buffer size for the write data cache, in bytes. Modifying this is not recommended; the default configuration is sufficient.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 | sink.buffer-count           | 3             | N        | Number of write data cache buffers. Modifying this is not recommended; the default configuration is sufficient.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
 | sink.max-retries            | 3             | N        | The maximum number of retries after a Commit failure. The default is 3.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |

diff --git a/docs/data-operate/import/data-source/amazon-s3.md b/docs/data-operate/import/data-source/amazon-s3.md
@@ -223,7 +223,7 @@ mysql> select * from test_s3load;
 
 <!-- Knowledge type: Configuration / Authentication -->
 
-In addition to using Access Key / Secret Key, Doris also supports authenticating S3 Load and TVF via `AWS Assume Role`. This is suitable for enterprises with restrictions on distributing credentials. For detailed configuration, see [AWS Integration - Assumed Role Authentication](../../../admin-manual/auth/integrations/aws-authentication-and-authorization.md#assumed-role-authentication).
+In addition to using Access Key / Secret Key, Doris also supports authenticating S3 Load and TVF via `AWS Assume Role`. This is suitable for enterprises with restrictions on distributing credentials. For detailed configuration, see [AWS Integration - Assumed Role Authentication](../../../admin-manual/auth/integrations/aws-authentication-and-authorization.md#assumed-role-authentication-and-authorization).
 
 ## FAQ
 
@@ -263,4 +263,4 @@ Increase `timeout` in `PROPERTIES` (in seconds) appropriately. The example uses
 ## Related documents
 
 - [Broker Load Manual](../import-way/broker-load-manual.md)
-- [AWS Integration - Assumed Role Authentication](../../../admin-manual/auth/integrations/aws-authentication-and-authorization.md#assumed-role-authentication)
+- [AWS Integration - Assumed Role Authentication](../../../admin-manual/auth/integrations/aws-authentication-and-authorization.md#assumed-role-authentication-and-authorization)
diff --git a/docs/data-operate/import/data-source/bigquery.md b/docs/data-operate/import/data-source/bigquery.md
@@ -228,7 +228,7 @@ Reason: column_name[country], the length of input is too long than schema. first
 Reason: column_name[country], the length of input is too long than schema. first 32 bytes of input str: [Australia] schema length: 1; actual length: 9; . src line [];
 ```
 
-For data quality errors, if skipping some erroneous rows is acceptable, set the error tolerance ratio in the S3 Load `PROPERTIES`. For details on the parameters, see [Load configuration parameters](../../import/import-way/broker-load-manual.md#related-configurations).
+For data quality errors, if skipping some erroneous rows is acceptable, set the error tolerance ratio in the S3 Load `PROPERTIES`. For details on the parameters, see [Load configuration parameters](../../import/import-way/broker-load-manual.md#advanced-configuration).
 
 #### 3.4 Import data from multiple files
 

diff --git a/docs/data-operate/import/data-source/snowflake.md b/docs/data-operate/import/data-source/snowflake.md
@@ -250,7 +250,7 @@ Reason: column_name[country], the length of input is too long than schema. first
 Reason: column_name[country], the length of input is too long than schema. first 32 bytes of input str: [Australia] schema length: 1;   actual length: 9; . src line [];
 ```
 
-For data quality errors, if some erroneous data is allowed to be skipped, you can set the error tolerance ratio in the `PROPERTIES` of the S3 Load job. For details, see [Import Configuration Parameters](../../import/import-way/broker-load-manual.md#related-configurations).
+For data quality errors, if some erroneous data is allowed to be skipped, you can set the error tolerance ratio in the `PROPERTIES` of the S3 Load job. For details, see [Import Configuration Parameters](../../import/import-way/broker-load-manual.md#advanced-configuration).
 
 #### 3.4 Batch Import Multiple Partitions
 
@@ -303,4 +303,4 @@ Doris does not have a type that fully corresponds to Snowflake's `TIME`. Therefo
 - [Azure Load](./azure-storage.md)
 - [TVF Load](./amazon-s3.md#method-2-load-with-tvf-synchronous)
 - [Load Best Practices](../load-best-practices/load-best-practices.md)
-- [Import Configuration Parameters](../../import/import-way/broker-load-manual.md#related-configurations)
+- [Import Configuration Parameters](../../import/import-way/broker-load-manual.md#advanced-configuration)