This is an automated email from the ASF dual-hosted git repository.
morningman pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new 618b8846354 fix(docs): use valid MDX comments in translation sources
(#4290)
618b8846354 is described below
commit 618b88463542c388ef5d477f53e4f17162fd5eb7
Author: Mingyu Chen (Rayner) <[email protected]>
AuthorDate: Thu Oct 15 06:57:11 2026 +0800
fix(docs): use valid MDX comments in translation sources (#4290)
## Summary
Replace HTML comments with MDX comments in 10 English and Chinese
documentation pages. The affected English pages fail the Japanese
translation runner's source preflight on current master, blocking
T09-DEV-083 and T09-DEV-084. The same syntax occurs in related 4.x and
community pages, so this change fixes those counterparts together.
Only comment delimiters change; rendered content, examples, URLs, and
page metadata stay the same.
## Validation
- The Japanese translation runner's source preflight checked all 10
changed pages with zero errors, including the shared CI structure
parser.
- `git diff --check` passed.
The blocked translation batches can be retried after this PR is merged
into master.
Co-authored-by: morningman <[email protected]>
---
community/how-to-contribute/community-badges.mdx | 4 +-
.../how-to-contribute/contribute-to-doris.mdx | 4 +-
docs/observability/overview.mdx | 14 ++---
.../incremental-materialized-view.mdx | 62 +++++++++++-----------
.../current/how-to-contribute/community-badges.mdx | 4 +-
.../how-to-contribute/contribute-to-doris.mdx | 4 +-
.../current/observability/overview.mdx | 14 ++---
.../incremental-materialized-view.mdx | 62 +++++++++++-----------
.../version-4.x/observability/overview.mdx | 14 ++---
.../version-4.x/observability/overview.mdx | 14 ++---
10 files changed, 98 insertions(+), 98 deletions(-)
diff --git a/community/how-to-contribute/community-badges.mdx
b/community/how-to-contribute/community-badges.mdx
index ab4175611ab..fe12938c386 100644
--- a/community/how-to-contribute/community-badges.mdx
+++ b/community/how-to-contribute/community-badges.mdx
@@ -19,7 +19,7 @@ import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
import Admonition from '@theme/Admonition';
-<!--
+{/*
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -36,7 +36,7 @@ software distributed under the License is distributed on an
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
--->
+*/}
<style>{`
/* ---------- hero ---------- */
diff --git a/community/how-to-contribute/contribute-to-doris.mdx
b/community/how-to-contribute/contribute-to-doris.mdx
index 85e005e21d8..a9dd589dab7 100644
--- a/community/how-to-contribute/contribute-to-doris.mdx
+++ b/community/how-to-contribute/contribute-to-doris.mdx
@@ -16,7 +16,7 @@ keywords:
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
-<!--
+{/*
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -33,7 +33,7 @@ software distributed under the License is distributed on an
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
--->
+*/}
<style>{`
.contribution-path-grid {
diff --git a/docs/observability/overview.mdx b/docs/observability/overview.mdx
index 10819d93e67..9ec5163260c 100644
--- a/docs/observability/overview.mdx
+++ b/docs/observability/overview.mdx
@@ -7,8 +7,8 @@
}
---
-<!-- Knowledge type: Architecture selection decision -->
-<!-- Applicable scenario: Observability platform construction / Technology
selection -->
+{/* Knowledge type: Architecture selection decision */}
+{/* Applicable scenario: Observability platform construction / Technology
selection */}
Observability is the ability to infer the internal state of a system from its
external output data. An observability platform collects, stores, and
visualizes three types of key data: **Logging, Tracing, and Metrics**. It helps
teams gain a comprehensive understanding of how distributed systems are
running, supports resource optimization, fault alerting, and root cause
analysis, and ultimately improves system reliability and user experience.
@@ -33,7 +33,7 @@ Observability platforms have become indispensable
infrastructure for modern dist
## How to Choose an Observability Solution
-<!-- Knowledge type: Architecture selection decision -->
+{/* Knowledge type: Architecture selection decision */}
### Key Characteristics of Observability Data
@@ -99,8 +99,8 @@ Based on the comparison above, **Doris has clear advantages
across all four dime
## Doris-Based Observability Solution
-<!-- Knowledge type: Architecture selection decision -->
-<!-- Applicable scenario: Observability platform construction -->
+{/* Knowledge type: Architecture selection decision */}
+{/* Applicable scenario: Observability platform construction */}
### System Architecture
@@ -147,8 +147,8 @@ A Doris-based observability platform consists of three core
components:
### Demo and Screenshots
-<!-- Knowledge type: Operational steps -->
-<!-- Applicable scenario: Solution experience / Demonstration -->
+{/* Knowledge type: Operational steps */}
+{/* Applicable scenario: Solution experience / Demonstration */}
The following uses a comprehensive
[Demo](https://github.com/apache/doris-opentelemetry-demo) from the
OpenTelemetry community to showcase a Doris-based observability platform.
diff --git
a/docs/query-acceleration/materialized-view/async-materialized-view/incremental-materialized-view.mdx
b/docs/query-acceleration/materialized-view/async-materialized-view/incremental-materialized-view.mdx
index f86c4997890..e5f2435ca91 100644
---
a/docs/query-acceleration/materialized-view/async-materialized-view/incremental-materialized-view.mdx
+++
b/docs/query-acceleration/materialized-view/async-materialized-view/incremental-materialized-view.mdx
@@ -30,8 +30,8 @@
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
-<!-- Knowledge type: Feature description / How-to guide / Parameter reference
/ Troubleshooting -->
-<!-- Use cases: Frequent base table inserts, updates and deletes / Small share
of changed rows / Expensive full or partition recomputation -->
+{/* Knowledge type: Feature description / How-to guide / Parameter reference /
Troubleshooting */}
+{/* Use cases: Frequent base table inserts, updates and deletes / Small share
of changed rows / Expensive full or partition recomputation */}
Incremental View Maintenance (IVM) maintains an asynchronous materialized view
based on row-level changes in its base tables. A regular asynchronous
materialized view recomputes all of its data or every affected partition; IVM
computes only the rows inserted, updated and deleted in the base tables between
two refreshes and applies those changes to the materialized view.
@@ -39,8 +39,8 @@ Incremental View Maintenance (IVM) maintains an asynchronous
materialized view b
IVM is available since Doris 5.0.0. It is experimental and disabled by
default. Before using it, enable Row Binlog and Table Stream in the FE
configuration. See [Prerequisites](#prerequisites).
:::
-<!-- Knowledge type: Scenario selection -->
-<!-- Use cases: Choosing IVM / Estimating refresh cost -->
+{/* Knowledge type: Scenario selection */}
+{/* Use cases: Choosing IVM / Estimating refresh cost */}
## When to use IVM
@@ -53,8 +53,8 @@ Compare the number of changed rows per refresh, the size of
the affected partiti
| Building the first baseline, small data volume, or recovering the IVM
baseline | Use `COMPLETE` | Recomputes all data of the materialized view |
| Results must be transactionally consistent with the base tables in real time
| Do not use an asynchronous materialized view | IVM still refreshes through
asynchronous tasks and does not provide real-time consistency |
-<!-- Knowledge type: Architecture decision -->
-<!-- Use cases: Choosing between INCREMENTAL / PARTITIONS / COMPLETE / AUTO -->
+{/* Knowledge type: Architecture decision */}
+{/* Use cases: Choosing between INCREMENTAL / PARTITIONS / COMPLETE / AUTO */}
## Differences from partition-level incremental refresh
@@ -69,8 +69,8 @@ Doris supports four refresh methods for asynchronous
materialized views. IVM cor
`INCREMENTAL FALLBACK` only changes how failures are handled at refresh time.
When the materialized view is created, its definition SQL must still satisfy
the IVM requirements; `FALLBACK` does not let an unsupported definition pass
the creation check.
-<!-- Knowledge type: How it works -->
-<!-- Use cases: Understanding the IVM data flow / Consistency mechanism -->
+{/* Knowledge type: How it works */}
+{/* Use cases: Understanding the IVM data flow / Consistency mechanism */}
## How it works
@@ -82,8 +82,8 @@ When a materialized view that supports IVM is created, Doris
creates an internal
At refresh time, Doris generates a delta plan from the unconsumed changes of
each base table. For join queries, it also reads a snapshot of the base tables
aligned with the consumption offsets, so that multi-table computation uses a
consistent data boundary. The materialized view data and the consumption
offsets are committed in the same transaction; if the transaction fails,
neither is committed.
-<!-- Knowledge type: Pre-deployment checklist -->
-<!-- Use cases: Enabling IVM / Evaluating tables before creation -->
+{/* Knowledge type: Pre-deployment checklist */}
+{/* Use cases: Enabling IVM / Evaluating tables before creation */}
## Prerequisites
@@ -124,8 +124,8 @@ PROPERTIES (
Row Binlog can only be enabled when the table is created and cannot be
disabled afterwards. For the full list of table model, column type, write
method and DDL restrictions, see [Row
Binlog](../../../data-operate/incremental/row-binlog).
-<!-- Knowledge type: Step-by-step guide -->
-<!-- Use cases: First-time setup / Feature verification -->
+{/* Knowledge type: Step-by-step guide */}
+{/* Use cases: First-time setup / Feature verification */}
## Quick start
@@ -269,8 +269,8 @@ LIMIT 1;
- `IvmFallbackReason` is empty when no IVM fallback happened; otherwise it
records a stable fallback reason.
- `ErrorMsg` records the details of a failed strict incremental refresh.
-<!-- Knowledge type: Compatibility reference / SQL examples -->
-<!-- Use cases: Evaluating SQL before creation / Diagnosing unsupported syntax
-->
+{/* Knowledge type: Compatibility reference / SQL examples */}
+{/* Use cases: Evaluating SQL before creation / Diagnosing unsupported syntax
*/}
## Supported queries
@@ -1075,8 +1075,8 @@ The following forms are not supported, and creation fails
with an explicit `REFR
- Using a regular asynchronous materialized view as a base table. Chained
maintenance requires the lower-level materialized view to be an IVM as well.
- Any other operation not listed in the table above.
-<!-- Knowledge type: Runtime behavior / Failure handling -->
-<!-- Use cases: Configuring the refresh strategy / Automatic refresh interval
/ Diagnosing IVM fallback / Rebuilding the baseline -->
+{/* Knowledge type: Runtime behavior / Failure handling */}
+{/* Use cases: Configuring the refresh strategy / Automatic refresh interval /
Diagnosing IVM fallback / Rebuilding the baseline */}
## Refresh and fallback
@@ -1219,8 +1219,8 @@ If the definition SQL can no longer be analyzed after a
base table change, for e
When an internal Stream is missing or can no longer be used, `INCREMENTAL
FALLBACK` and `AUTO` run `COMPLETE` directly with `IvmFallbackReason`
`STREAM_UNSUPPORTED`; a `COMPLETE` refresh rebuilds the internal Streams and
realigns the consumption offsets. A strict `INCREMENTAL` refresh fails, and you
need to run `COMPLETE` or `AUTO` once.
-<!-- Knowledge type: Troubleshooting -->
-<!-- Use cases: Verifying the delta plan / Previewing refresh data -->
+{/* Knowledge type: Troubleshooting */}
+{/* Use cases: Verifying the delta plan / Previewing refresh data */}
## Previewing and explaining the delta plan
@@ -1260,8 +1260,8 @@ The result contains the rows the refresh would actually
write, so besides the bu
`DRY RUN` only supports the `INCREMENTAL` refresh of an IVM. It cannot be
combined with `COMPLETE`, `EXPLAIN` or partition refresh.
-<!-- Knowledge type: Operations -->
-<!-- Use cases: Monitoring internal Streams / Lifecycle management -->
+{/* Knowledge type: Operations */}
+{/* Use cases: Monitoring internal Streams / Lifecycle management */}
## Internal Table Streams
@@ -1288,8 +1288,8 @@ Internal Streams start with `__doris_ivm_stream_` and are
reserved for IVM. Do n
For the offset, snapshot and concurrency semantics of Table Streams, see
[Table Stream Basics](../../../data-operate/incremental/table-stream) and
[Table Stream
Advanced](../../../data-operate/incremental/table-stream-advanced).
-<!-- Knowledge type: Configuration parameters -->
-<!-- Use cases: IVM key design / Incremental partition window / Refresh
resource control -->
+{/* Knowledge type: Configuration parameters */}
+{/* Use cases: IVM key design / Incremental partition window / Refresh
resource control */}
## IVM properties
@@ -1349,8 +1349,8 @@ Only exclude dimension tables that rarely change, or
tables whose changes may wa
For all materialized view properties, see [CREATE ASYNC MATERIALIZED
VIEW](../../../sql-manual/sql-statements/table-and-view/async-materialized-view/CREATE-ASYNC-MATERIALIZED-VIEW).
-<!-- Knowledge type: Limitations -->
-<!-- Use cases: Production readiness / Performance risk review -->
+{/* Knowledge type: Limitations */}
+{/* Use cases: Production readiness / Performance risk review */}
## Limitations and notes
@@ -1361,8 +1361,8 @@ For all materialized view properties, see [CREATE ASYNC
MATERIALIZED VIEW](../..
- `MIN`, `MAX` and Bitmap aggregations require a complete recomputation in
some delete scenarios. In production, use `INCREMENTAL FALLBACK` or `AUTO` and
monitor `IvmFallbackReason`.
- The table model, column type, schema change and delete restrictions of Row
Binlog apply directly to IVM. See [Supported scope and limitations of Row
Binlog](../../../data-operate/incremental/row-binlog#supported-scope-and-limitations).
-<!-- Knowledge type: FAQ / Troubleshooting -->
-<!-- Use cases: Creation failure / Refresh fallback / Baseline rebuild / Data
latency -->
+{/* Knowledge type: FAQ / Troubleshooting */}
+{/* Use cases: Creation failure / Refresh fallback / Baseline rebuild / Data
latency */}
## FAQ
@@ -1379,8 +1379,8 @@ When creation fails, a refresh falls back, or the data is
not updated, use the t
| The view is not updated after an excluded base table changes on its own |
Tables in `excluded_trigger_tables` do not trigger refreshes on their own. Wait
for a refresh triggered by other base tables, or run a `COMPLETE` refresh.
After the table is removed from `excluded_trigger_tables`, the next refresh
rebuilds the whole materialized view |
| Can internal Streams be consumed or reset manually | No. Internal Streams
are reserved for IVM; Doris manages their lifecycle and consumption offsets |
-<!-- Knowledge type: Best practices -->
-<!-- Use cases: Production deployment / Resource planning / Ongoing operations
-->
+{/* Knowledge type: Best practices */}
+{/* Use cases: Production deployment / Resource planning / Ongoing operations
*/}
## Best practices
@@ -1393,8 +1393,8 @@ When creation fails, a refresh falls back, or the data is
not updated, use the t
7. **Monitor tasks and Stream backlog.** Watch `tasks("type"="mv")`,
`mv_infos` and `information_schema.table_stream_consumption` together.
8. **Review fallback reasons regularly.** Occasional fallbacks protect
correctness; continuous fallbacks indicate that the query shape, Binlog
continuity or the baseline needs attention.
-<!-- Knowledge type: Step-by-step guide -->
-<!-- Use cases: Cleaning up the example environment -->
+{/* Knowledge type: Step-by-step guide */}
+{/* Use cases: Cleaning up the example environment */}
## Cleaning up the example
@@ -1406,7 +1406,7 @@ DROP DATABASE ivm_demo;
When an IVM is dropped, Doris also cleans up its internal Table Streams. No
separate `DROP STREAM` is needed.
-<!-- Knowledge type: Navigation -->
+{/* Knowledge type: Navigation */}
## See also
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/community-badges.mdx
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/community-badges.mdx
index 8b6d9e7e6bc..ff4d31e5984 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/community-badges.mdx
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/community-badges.mdx
@@ -19,7 +19,7 @@ import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
import Admonition from '@theme/Admonition';
-<!--
+{/*
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -36,7 +36,7 @@ software distributed under the License is distributed on an
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
--->
+*/}
<style>{`
/* ---------- hero ---------- */
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-to-doris.mdx
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-to-doris.mdx
index 74dcddb1b61..582421a3c4e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-to-doris.mdx
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute/contribute-to-doris.mdx
@@ -16,7 +16,7 @@ keywords:
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
-<!--
+{/*
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -33,7 +33,7 @@ software distributed under the License is distributed on an
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
--->
+*/}
<style>{`
.contribution-path-grid {
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/overview.mdx
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/overview.mdx
index 8a8ccc2be1f..d186bd23c10 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/overview.mdx
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/observability/overview.mdx
@@ -7,8 +7,8 @@
}
---
-<!-- 知识类型: 架构选型决策 -->
-<!-- 适用场景: 可观测性平台建设 / 技术选型 -->
+{/* 知识类型: 架构选型决策 */}
+{/* 适用场景: 可观测性平台建设 / 技术选型 */}
可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台围绕
**日志（Logging）、链路追踪（Tracing）、指标（Metrics）**
三类关键数据进行采集、存储与可视化分析，帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等工作，最终提升系统可靠性与用户体验。
@@ -33,7 +33,7 @@
## 怎么选择可观测性解决方案
-<!-- 知识类型: 架构选型决策 -->
+{/* 知识类型: 架构选型决策 */}
### 可观测性数据的关键特点
@@ -99,8 +99,8 @@
## 基于 Doris 的可观测性解决方案
-<!-- 知识类型: 架构选型决策 -->
-<!-- 适用场景: 可观测性平台建设 -->
+{/* 知识类型: 架构选型决策 */}
+{/* 适用场景: 可观测性平台建设 */}
### 系统架构
@@ -147,8 +147,8 @@ Doris 是一个现代化数据仓库，采用 MPP 分布式架构，结合向量
### Demo 与截图
-<!-- 知识类型: 操作步骤 -->
-<!-- 适用场景: 方案体验 / 演示 -->
+{/* 知识类型: 操作步骤 */}
+{/* 适用场景: 方案体验 / 演示 */}
下面以 OpenTelemetry 社区的一个全方位
[Demo](https://github.com/apache/doris-opentelemetry-demo) 来展示基于 Doris 的可观测性平台。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/incremental-materialized-view.mdx
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/incremental-materialized-view.mdx
index 639db62e10c..6c6feb31c88 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/incremental-materialized-view.mdx
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/materialized-view/async-materialized-view/incremental-materialized-view.mdx
@@ -30,8 +30,8 @@
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
-<!-- 知识类型: 功能说明 / 操作指南 / 参数参考 / 故障排查 -->
-<!-- 适用场景: 基表频繁增删改 / 变化行数占比较小 / 全量或分区重算成本高 -->
+{/* 知识类型: 功能说明 / 操作指南 / 参数参考 / 故障排查 */}
+{/* 适用场景: 基表频繁增删改 / 变化行数占比较小 / 全量或分区重算成本高 */}
物化视图增量维护（Incremental View
Maintenance，IVM）根据基表的行级变化维护异步物化视图。普通异步物化视图会重算全部数据或受影响的整个分区；IVM
只计算基表两次刷新之间的新增、更新和删除，并把这些变化应用到物化视图。
@@ -39,8 +39,8 @@ import TabItem from '@theme/TabItem';
IVM 从 Doris 5.0.0 开始支持，目前处于实验阶段，默认关闭。使用前需要在 FE 配置中开启 Row Binlog 和 Table
Stream，详见 [前置条件](#前置条件)。
:::
-<!-- 知识类型: 场景选型 -->
-<!-- 适用场景: IVM 选型 / 刷新成本评估 -->
+{/* 知识类型: 场景选型 */}
+{/* 适用场景: IVM 选型 / 刷新成本评估 */}
## 适用场景
@@ -53,8 +53,8 @@ IVM 从 Doris 5.0.0 开始支持，目前处于实验阶段，默认关闭。使
| 首次建立基线、数据量较小或需要恢复 IVM 基线 | 使用 `COMPLETE` | 重新计算物化视图的全部数据 |
| 要求与基表事务同步、实时一致 | 不使用异步物化视图 | IVM 仍通过异步任务刷新，不提供实时一致性 |
-<!-- 知识类型: 架构决策 -->
-<!-- 适用场景: INCREMENTAL / PARTITIONS / COMPLETE / AUTO 选型 -->
+{/* 知识类型: 架构决策 */}
+{/* 适用场景: INCREMENTAL / PARTITIONS / COMPLETE / AUTO 选型 */}
## 与分区增量刷新的区别
@@ -69,8 +69,8 @@ Doris 支持四种异步物化视图刷新方式。IVM 对应 `INCREMENTAL`，
`INCREMENTAL FALLBACK` 只改变刷新运行时的失败处理。创建物化视图时，定义 SQL 仍必须满足 IVM 要求；`FALLBACK`
不会让不支持 IVM 的定义通过创建检查。
-<!-- 知识类型: 工作原理 -->
-<!-- 适用场景: 理解 IVM 数据流 / 一致性机制 -->
+{/* 知识类型: 工作原理 */}
+{/* 适用场景: 理解 IVM 数据流 / 一致性机制 */}
## 工作原理
@@ -82,8 +82,8 @@ IVM 复用 Doris 的 Row Binlog 和 Table Stream 能力：
刷新时，Doris
根据每张基表的未消费变化生成增量计划。关联查询还会读取与消费位点对齐的基表快照，保证多表计算使用一致的数据边界。物化视图数据和消费位点在同一个事务中提交；事务失败时，两者都不会提交。
-<!-- 知识类型: 部署前检查 -->
-<!-- 适用场景: 启用 IVM / 建表前评估 -->
+{/* 知识类型: 部署前检查 */}
+{/* 适用场景: 启用 IVM / 建表前评估 */}
## 前置条件
@@ -124,8 +124,8 @@ PROPERTIES (
Row Binlog 只能在建表时开启，开启后不能关闭。完整的表模型、列类型、写入方式和 DDL 限制见 [Row
Binlog](../../../data-operate/incremental/row-binlog)。
-<!-- 知识类型: 操作步骤 -->
-<!-- 适用场景: 首次配置 / 功能验证 -->
+{/* 知识类型: 操作步骤 */}
+{/* 适用场景: 首次配置 / 功能验证 */}
## 快速上手
@@ -269,8 +269,8 @@ LIMIT 1;
- `IvmFallbackReason` 为空表示没有发生 IVM 回退；非空时记录稳定的回退原因。
- `ErrorMsg` 记录严格增量刷新失败的具体信息。
-<!-- 知识类型: 兼容性参考 / SQL 示例 -->
-<!-- 适用场景: 创建前 SQL 评估 / 不支持语法排查 -->
+{/* 知识类型: 兼容性参考 / SQL 示例 */}
+{/* 适用场景: 创建前 SQL 评估 / 不支持语法排查 */}
## 支持的查询
@@ -1075,8 +1075,8 @@ GROUP BY channel;
- 使用普通异步物化视图作为基表。链式维护要求下层物化视图本身也是 IVM。
- 上文表格之外的其他运算。
-<!-- 知识类型: 运行机制 / 故障处理 -->
-<!-- 适用场景: 刷新策略配置 / 自动刷新间隔 / IVM 回退排查 / 基线恢复 -->
+{/* 知识类型: 运行机制 / 故障处理 */}
+{/* 适用场景: 刷新策略配置 / 自动刷新间隔 / IVM 回退排查 / 基线恢复 */}
## 刷新和回退
@@ -1219,8 +1219,8 @@ IVM -> PARTITIONS -> COMPLETE
内部 Stream 缺失或无法继续使用时，`INCREMENTAL FALLBACK` 和 `AUTO` 直接执行
`COMPLETE`，`IvmFallbackReason` 为 `STREAM_UNSUPPORTED`；`COMPLETE` 刷新会重建内部 Stream
并重新对齐消费位点。严格 `INCREMENTAL` 刷新会失败，需要执行一次 `COMPLETE` 或 `AUTO`。
-<!-- 知识类型: 故障排查 -->
-<!-- 适用场景: 增量计划验证 / 刷新数据预览 -->
+{/* 知识类型: 故障排查 */}
+{/* 适用场景: 增量计划验证 / 刷新数据预览 */}
## 预览和解释增量计划
@@ -1260,8 +1260,8 @@ REFRESH MATERIALIZED VIEW <mv_name> INCREMENTAL WITH DRY
RUN LIMIT 100 OFFSET 20
`DRY RUN` 只支持 IVM 的 `INCREMENTAL` 刷新，不能与 `COMPLETE`、`EXPLAIN` 或分区刷新组合使用。
-<!-- 知识类型: 运维说明 -->
-<!-- 适用场景: 内部 Stream 监控 / 生命周期管理 -->
+{/* 知识类型: 运维说明 */}
+{/* 适用场景: 内部 Stream 监控 / 生命周期管理 */}
## 内部 Table Stream
@@ -1288,8 +1288,8 @@ WHERE Name = "<mv_name>";
Table Stream 的位点、快照和并发语义见 [Table Stream
基础](../../../data-operate/incremental/table-stream) 和 [Table Stream
进阶](../../../data-operate/incremental/table-stream-advanced)。
-<!-- 知识类型: 配置参数 -->
-<!-- 适用场景: IVM Key 设计 / 增量分区窗口 / 刷新资源控制 -->
+{/* 知识类型: 配置参数 */}
+{/* 适用场景: IVM Key 设计 / 增量分区窗口 / 刷新资源控制 */}
## IVM 属性
@@ -1349,8 +1349,8 @@ PROPERTIES (
所有物化视图属性见 [CREATE ASYNC MATERIALIZED
VIEW](../../../sql-manual/sql-statements/table-and-view/async-materialized-view/CREATE-ASYNC-MATERIALIZED-VIEW)。
-<!-- 知识类型: 使用限制 -->
-<!-- 适用场景: 生产上线评估 / 性能风险检查 -->
+{/* 知识类型: 使用限制 */}
+{/* 适用场景: 生产上线评估 / 性能风险检查 */}
## 限制和注意事项
@@ -1361,8 +1361,8 @@ PROPERTIES (
- `MIN`、`MAX` 和 Bitmap 聚合在部分删除场景下需要完整重算。生产环境建议使用 `INCREMENTAL FALLBACK` 或
`AUTO`，并监控 `IvmFallbackReason`。
- Row Binlog 的表模型、列类型、Schema Change 和删除行为限制会直接影响 IVM，详见 [Row Binlog
的支持范围与限制](../../../data-operate/incremental/row-binlog#支持范围与限制)。
-<!-- 知识类型: 常见问题 / 故障排查 -->
-<!-- 适用场景: 创建失败 / 刷新回退 / 基线重建 / 数据延迟 -->
+{/* 知识类型: 常见问题 / 故障排查 */}
+{/* 适用场景: 创建失败 / 刷新回退 / 基线重建 / 数据延迟 */}
## 常见问题
@@ -1379,8 +1379,8 @@ PROPERTIES (
| 被排除的基表单独变化后，视图数据未更新 | `excluded_trigger_tables`
中的表不会独立触发刷新。等待其他基表变化触发刷新，或者执行一次 `COMPLETE` 刷新。把该表从 `excluded_trigger_tables`
中移除后，下一次刷新会完整重建物化视图 |
| 能否手工消费或重置内部 Stream | 不能。内部 Stream 仅供 IVM 使用，由 Doris 管理生命周期和消费位点 |
-<!-- 知识类型: 最佳实践 -->
-<!-- 适用场景: 生产部署 / 资源规划 / 持续运维 -->
+{/* 知识类型: 最佳实践 */}
+{/* 适用场景: 生产部署 / 资源规划 / 持续运维 */}
## 最佳实践
@@ -1393,8 +1393,8 @@ PROPERTIES (
7. **监控任务和 Stream 积压。** 同时观察 `tasks("type"="mv")`、`mv_infos` 和
`information_schema.table_stream_consumption`。
8. **定期检查回退原因。** 偶发回退可以保证正确性；持续回退说明查询形态、Binlog 连续性或基线需要处理。
-<!-- 知识类型: 操作步骤 -->
-<!-- 适用场景: 示例环境清理 -->
+{/* 知识类型: 操作步骤 */}
+{/* 适用场景: 示例环境清理 */}
## 清理示例
@@ -1406,7 +1406,7 @@ DROP DATABASE ivm_demo;
删除 IVM 时，Doris 会一并清理其内部 Table Stream，不需要单独执行 `DROP STREAM`。
-<!-- 知识类型: 文档导航 -->
+{/* 知识类型: 文档导航 */}
## 更多参考
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/overview.mdx
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/overview.mdx
index 8a8ccc2be1f..d186bd23c10 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/overview.mdx
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/observability/overview.mdx
@@ -7,8 +7,8 @@
}
---
-<!-- 知识类型: 架构选型决策 -->
-<!-- 适用场景: 可观测性平台建设 / 技术选型 -->
+{/* 知识类型: 架构选型决策 */}
+{/* 适用场景: 可观测性平台建设 / 技术选型 */}
可观测性（Observability）是指通过系统的外部输出数据来推断其内部状态的能力。可观测性平台围绕
**日志（Logging）、链路追踪（Tracing）、指标（Metrics）**
三类关键数据进行采集、存储与可视化分析，帮助团队全面理解分布式系统的运行状态，支撑资源优化、故障预警、根因分析等工作，最终提升系统可靠性与用户体验。
@@ -33,7 +33,7 @@
## 怎么选择可观测性解决方案
-<!-- 知识类型: 架构选型决策 -->
+{/* 知识类型: 架构选型决策 */}
### 可观测性数据的关键特点
@@ -99,8 +99,8 @@
## 基于 Doris 的可观测性解决方案
-<!-- 知识类型: 架构选型决策 -->
-<!-- 适用场景: 可观测性平台建设 -->
+{/* 知识类型: 架构选型决策 */}
+{/* 适用场景: 可观测性平台建设 */}
### 系统架构
@@ -147,8 +147,8 @@ Doris 是一个现代化数据仓库，采用 MPP 分布式架构，结合向量
### Demo 与截图
-<!-- 知识类型: 操作步骤 -->
-<!-- 适用场景: 方案体验 / 演示 -->
+{/* 知识类型: 操作步骤 */}
+{/* 适用场景: 方案体验 / 演示 */}
下面以 OpenTelemetry 社区的一个全方位
[Demo](https://github.com/apache/doris-opentelemetry-demo) 来展示基于 Doris 的可观测性平台。
diff --git a/versioned_docs/version-4.x/observability/overview.mdx
b/versioned_docs/version-4.x/observability/overview.mdx
index 10819d93e67..9ec5163260c 100644
--- a/versioned_docs/version-4.x/observability/overview.mdx
+++ b/versioned_docs/version-4.x/observability/overview.mdx
@@ -7,8 +7,8 @@
}
---
-<!-- Knowledge type: Architecture selection decision -->
-<!-- Applicable scenario: Observability platform construction / Technology
selection -->
+{/* Knowledge type: Architecture selection decision */}
+{/* Applicable scenario: Observability platform construction / Technology
selection */}
Observability is the ability to infer the internal state of a system from its
external output data. An observability platform collects, stores, and
visualizes three types of key data: **Logging, Tracing, and Metrics**. It helps
teams gain a comprehensive understanding of how distributed systems are
running, supports resource optimization, fault alerting, and root cause
analysis, and ultimately improves system reliability and user experience.
@@ -33,7 +33,7 @@ Observability platforms have become indispensable
infrastructure for modern dist
## How to Choose an Observability Solution
-<!-- Knowledge type: Architecture selection decision -->
+{/* Knowledge type: Architecture selection decision */}
### Key Characteristics of Observability Data
@@ -99,8 +99,8 @@ Based on the comparison above, **Doris has clear advantages
across all four dime
## Doris-Based Observability Solution
-<!-- Knowledge type: Architecture selection decision -->
-<!-- Applicable scenario: Observability platform construction -->
+{/* Knowledge type: Architecture selection decision */}
+{/* Applicable scenario: Observability platform construction */}
### System Architecture
@@ -147,8 +147,8 @@ A Doris-based observability platform consists of three core
components:
### Demo and Screenshots
-<!-- Knowledge type: Operational steps -->
-<!-- Applicable scenario: Solution experience / Demonstration -->
+{/* Knowledge type: Operational steps */}
+{/* Applicable scenario: Solution experience / Demonstration */}
The following uses a comprehensive
[Demo](https://github.com/apache/doris-opentelemetry-demo) from the
OpenTelemetry community to showcase a Doris-based observability platform.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
