[opt](temp-table) notice temp-table is a experimental feature

docs-next/table-design/temporary-table.md

@@ -1,11 +1,16 @@
 ---
 {
-    "title": "Temporary Table",
+    "title": "Temporary Table (Experimental)",
     "language": "en",
     "description": "A Doris temporary table is a session-scoped materialized internal table used to break down complex SQL queries and store intermediate computation results. It is automatically dropped when the session ends, with no manual cleanup required."
 }
 ---
 
+:::note
+
+The temporary table is an experimental feature. It is not recommended for use in a production environment.
+:::
+
 <!-- Knowledge type: Feature -->
 <!-- Applicable scenarios: Complex SQL decomposition / Intermediate result staging / Data debugging -->
 

docs/table-design/temporary-table.md

@@ -1,11 +1,16 @@
 ---
 {
-    "title": "Temporary Table",
+    "title": "Temporary Table (Experimental)",
     "language": "en",
     "description": "When performing complex data processing tasks, breaking down large SQL queries into multiple steps and temporarily saving the results of each step as "
 }
 ---
 
+:::note
+
+The temporary table is an experimental feature. It is not recommended for use in a production environment.
+:::
+
 When performing complex data processing tasks, breaking down large SQL queries into multiple steps and temporarily saving the results of each step as physical tables is an effective strategy. This method can significantly reduce the complexity of SQL queries and enhance data debuggability. However, it is important to note that these physical tables must be manually cleaned up after they have served their purpose. If non-physical temporary tables are preferred, Doris currently only supports defining them via the `WITH` clause.
 
 To address the above issues, Doris introduces the temporary table feature. Temporary tables are temporarily existing materialized internal tables with the following key characteristics:

i18n/zh-CN/docusaurus-plugin-content-docs-next/current/table-design/temporary-table.md

@@ -1,11 +1,16 @@
 ---
 {
-    "title": "临时表",
+    "title": "临时表（实验功能）",
     "language": "zh-CN",
     "description": "Doris 临时表（Temporary Table）是会话级物化内表，用于拆分复杂 SQL 查询、保存中间计算结果，会话结束后自动删除，无需手动清理。"
 }
 ---
 
+:::note
+
+临时表是一个实验性质的功能。不推荐在生产环境使用。
+:::
+
 <!-- 知识类型: 功能特性 -->
 <!-- 适用场景: 复杂 SQL 拆分 / 中间结果暂存 / 数据调试 -->
 

i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/temporary-table.md

@@ -1,11 +1,16 @@
 ---
 {
-    "title": "临时表",
+    "title": "临时表（实验功能）",
     "language": "zh-CN",
     "description": "在进行复杂的数据处理任务时，将大型 SQL 查询拆分为多个步骤，并将每个步骤的计算结果临时保存为实体表，是一种有效的策略。这种方法能够显著降低 SQL 查询的复杂度，并提升数据的可调试性。然而，需要注意的是，实体表在完成其使用目的后，需要手动进行清理。若选择使用非实体临时表，"
 }
 ---
 
+:::note
+
+临时表是一个实验性质的功能。不推荐在生产环境使用。
+:::
+
 在进行复杂的数据处理任务时，将大型 SQL 查询拆分为多个步骤，并将每个步骤的计算结果临时保存为实体表，是一种有效的策略。这种方法能够显著降低 SQL 查询的复杂度，并提升数据的可调试性。然而，需要注意的是，实体表在完成其使用目的后，需要手动进行清理。若选择使用非实体临时表，当前 Doris 仅支持通过 `WITH` 子句进行定义。
 
 为了解决上述问题，Doris 引入了临时表功能。临时表是一种临时存在的物化内表，具备以下关键特性：

i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/temporary-table.md

@@ -1,11 +1,16 @@
 ---
 {
-    "title": "临时表",
+    "title": "临时表（实验功能）",
     "language": "zh-CN",
     "description": "在进行复杂的数据处理任务时，将大型 SQL 查询拆分为多个步骤，并将每个步骤的计算结果临时保存为实体表，是一种有效的策略。这种方法能够显著降低 SQL 查询的复杂度，并提升数据的可调试性。然而，需要注意的是，实体表在完成其使用目的后，需要手动进行清理。若选择使用非实体临时表，"
 }
 ---
 
+:::note
+
+临时表是一个实验性质的功能。不推荐在生产环境使用。
+:::
+
 在进行复杂的数据处理任务时，将大型 SQL 查询拆分为多个步骤，并将每个步骤的计算结果临时保存为实体表，是一种有效的策略。这种方法能够显著降低 SQL 查询的复杂度，并提升数据的可调试性。然而，需要注意的是，实体表在完成其使用目的后，需要手动进行清理。若选择使用非实体临时表，当前 Doris 仅支持通过 `WITH` 子句进行定义。
 
 为了解决上述问题，Doris 引入了临时表功能。临时表是一种临时存在的物化内表，具备以下关键特性：

versioned_docs/version-4.x/table-design/temporary-table.md

@@ -1,11 +1,16 @@
 ---
 {
-    "title": "Temporary Table",
+    "title": "Temporary Table (Experimental)",
     "language": "en",
     "description": "When performing complex data processing tasks, breaking down large SQL queries into multiple steps and temporarily saving the results of each step as "
 }
 ---
 
+:::note
+
+The temporary table is an experimental feature. It is not recommended for use in a production environment.
+:::
+
 When performing complex data processing tasks, breaking down large SQL queries into multiple steps and temporarily saving the results of each step as physical tables is an effective strategy. This method can significantly reduce the complexity of SQL queries and enhance data debuggability. However, it is important to note that these physical tables must be manually cleaned up after they have served their purpose. If non-physical temporary tables are preferred, Doris currently only supports defining them via the `WITH` clause.
 
 To address the above issues, Doris introduces the temporary table feature. Temporary tables are temporarily existing materialized internal tables with the following key characteristics: