This is an automated email from the ASF dual-hosted git repository.
morrySnow 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 2ec4dce96b1 [doc](table) deprecate temporary table documentation
(#4153)
2ec4dce96b1 is described below
commit 2ec4dce96b1f4428811a3444bb82d733d74f9ce1
Author: morrySnow <[email protected]>
AuthorDate: Fri Sep 18 10:34:39 2026 +0800
[doc](table) deprecate temporary table documentation (#4153)
## Versions
- [x] dev
- [x] 4.x
- [ ] 3.x
- [ ] 2.1 or older (not covered by version/language sync gate)
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [x] Checked by AI
- [ ] Test Cases Built — not applicable for this docs-only change
- [x] Updated required version and language counterparts, or explained
why not
- [x] If only one language changed, confirmed whether source/translation
counterparts need sync
## Summary
- remove the Temporary Table documentation, sidebar entry, and overview
cards from dev
- mark the 4.x English and Chinese pages and overview cards as
deprecated
- keep the 4.x sidebar entry so existing versioned documentation remains
reachable
## Validation
- git diff --check
- validated JSON front matter and versioned sidebar JSON
- confirmed dev has no remaining temporary-table page references
- yarn docs:links:changed was not run because local dependencies are
missing gray-matter
---
docs/table-design/overview.mdx | 6 --
docs/table-design/temporary-table.md | 66 ----------------------
.../current/table-design/overview.mdx | 6 --
.../current/table-design/temporary-table.md | 66 ----------------------
.../version-4.x/table-design/overview.mdx | 4 +-
.../version-4.x/table-design/temporary-table.md | 8 +--
sidebars.ts | 1 -
.../version-4.x/table-design/overview.mdx | 4 +-
.../version-4.x/table-design/temporary-table.md | 8 +--
9 files changed, 12 insertions(+), 157 deletions(-)
diff --git a/docs/table-design/overview.mdx b/docs/table-design/overview.mdx
index 494cc61a700..eb318572e53 100644
--- a/docs/table-design/overview.mdx
+++ b/docs/table-design/overview.mdx
@@ -232,12 +232,6 @@ Table properties apply at the partition level. Modifying
table properties only t
## Special Tables and Best Practices
<div className="cards-grid">
-<GettingStartedCard
- title="Temporary Tables"
- description="Break complex SQL into multiple steps and stage intermediate
results for easier debugging and reuse"
- link="./temporary-table"
-/>
-
<GettingStartedCard
title="Table Design Best Practices"
description="A summary of key design recommendations for table models, Key
columns, partitioning and bucketing, indexes, and more"
diff --git a/docs/table-design/temporary-table.md
b/docs/table-design/temporary-table.md
deleted file mode 100644
index b0c67782a10..00000000000
--- a/docs/table-design/temporary-table.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-{
- "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 -->
-
-When working on complex data processing tasks, an effective strategy is to
break a large SQL query into multiple steps and temporarily save the result of
each step as a materialized table. This approach significantly reduces the
complexity of SQL queries and improves the debuggability of the data. However,
materialized tables must be cleaned up manually after they have served their
purpose. If you choose to use non-materialized temporary tables, Doris
currently only supports defining the [...]
-
-To address these issues, Doris introduces the **Temporary Table** feature. A
temporary table is a transiently existing materialized internal table. It
simplifies the storage and management of temporary data during complex data
processing while further enhancing the flexibility and safety of data
processing.
-
-## Core Features
-
-| Feature | Description |
-| --- | --- |
-| **Session-bound** | A temporary table only exists in the session that
created it, and its lifecycle is tightly bound to the current session. When the
session ends, all temporary tables created in that session are dropped
automatically. |
-| **Visible only within the session** | The visibility of a temporary table is
strictly limited to the session that created it. Even another session started
by the same user at the same time cannot access these temporary tables. |
-| **Flexible naming** | The names of temporary tables are not subject to the
uniqueness constraint. You can create temporary tables with the same name in
different sessions, and you can also create a temporary table with the same
name as another internal table. |
-
-:::info Note
-Like internal tables, a temporary table must be created under a Database
within the Internal Catalog.
-
-If a temporary table and a non-temporary table with the same name exist in the
same Database, the temporary table has the highest access priority. Within that
session, all queries and operations against tables with that name take effect
on the temporary table only (with the exception of creating materialized views).
-:::
-
-## Applicable Scenarios
-
-Temporary tables are suitable for the following data processing scenarios:
-
-- **Complex SQL decomposition**: Break a large query into multiple steps and
progressively materialize the intermediate results to reduce the complexity of
a single SQL statement.
-- **Intermediate result staging**: Store intermediate computation results
during ETL, data exploration, or report development to avoid repeated
computation.
-- **Data debugging and verification**: Materialize the result of each step to
make it easier to inspect and verify, improving debuggability.
-- **Session-isolated data processing**: Scenarios where data needs to be
visible within the session and reclaimed automatically when the session ends,
avoiding pollution from leftover data.
-
-## Usage
-
-### Create a Temporary Table
-
-Tables of any model can be defined as temporary tables, including the Unique,
Aggregate, and Duplicate models. You can create a temporary table by adding the
`TEMPORARY` keyword in the following SQL statements:
-
-- [CREATE
TABLE](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md)
-- [CREATE TABLE AS
SELECT](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md)
-- [CREATE TABLE
LIKE](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md)
-
-### Operate on a Temporary Table
-
-Other usage of temporary tables is essentially the same as that of regular
internal tables. Apart from the `CREATE` statements above, other DDL and DML
statements do not require the `TEMPORARY` keyword.
-
-## Limitations
-
-- Temporary tables can only be created in the Internal Catalog.
-- The ENGINE must be OLAP when creating the table.
-- Modifying a temporary table with an Alter statement is not supported.
-- Because of their transient nature, creating views and materialized views
based on a temporary table is not supported.
-- Backing up temporary tables and synchronizing them via Sync Job are not
supported.
-- Export, Stream Load, Broker Load, S3 Load, Mysql Load, and Routine Load are
not supported.
-- When a temporary table is dropped, it is permanently deleted without going
to the recycle bin.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/overview.mdx
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/overview.mdx
index 826d58373d1..b64fbf80603 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/overview.mdx
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/overview.mdx
@@ -232,12 +232,6 @@ Doris 中表名默认大小写敏感，最大长度为 64 字节。可通过以
## 特殊表与最佳实践
<div className="cards-grid">
-<GettingStartedCard
- title="临时表"
- description="将复杂 SQL 拆分为多步并暂存中间结果，便于调试与复用"
- link="./temporary-table"
-/>
-
<GettingStartedCard
title="建表最佳实践"
description="汇总表模型、Key 列、分区分桶、索引等关键设计建议"
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/temporary-table.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/temporary-table.md
deleted file mode 100644
index a829b4d924a..00000000000
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/table-design/temporary-table.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-{
- "title": "临时表（实验功能）",
- "language": "zh-CN",
- "description": "Doris 临时表（Temporary Table）是会话级物化内表，用于拆分复杂 SQL
查询、保存中间计算结果，会话结束后自动删除，无需手动清理。"
-}
----
-
-:::note
-
-临时表是一个实验性质的功能。不推荐在生产环境使用。
-:::
-
-<!-- 知识类型: 功能特性 -->
-<!-- 适用场景: 复杂 SQL 拆分 / 中间结果暂存 / 数据调试 -->
-
-在进行复杂的数据处理任务时，将大型 SQL 查询拆分为多个步骤，并将每个步骤的计算结果临时保存为实体表，是一种有效的策略。这种方法能够显著降低 SQL
查询的复杂度，并提升数据的可调试性。然而，实体表在完成其使用目的后，需要手动进行清理；若选择使用非实体临时表，当前 Doris 仅支持通过 `WITH`
子句进行定义。
-
-为了解决上述问题，Doris 引入了**临时表（Temporary
Table）**功能。临时表是一种临时存在的物化内表，能够在简化复杂数据处理过程中临时数据存储与管理的同时，进一步增强数据处理的灵活性和安全性。
-
-## 核心特性
-
-| 特性 | 说明 |
-| --- | --- |
-| **会话绑定** | 临时表仅存在于创建它的会话（Session）中，生命周期与当前会话紧密绑定。当会话结束时，该会话内创建的临时表会自动被删除。 |
-| **会话内可见** | 临时表的可见性严格限制在创建它的会话范围内。即使是同一用户在同一时间启动的另一个会话，也无法访问这些临时表。 |
-| **命名灵活** | 临时表的命名不受唯一性约束。可以在不同 Session 中创建同名临时表，也可以创建与其他内表同名的临时表。 |
-
-:::info 备注
-与内表类似，临时表必须在 Internal Catalog 内的某个 Database 下创建。
-
-如果同一 Database 中同时存在同名的临时表和非临时表，临时表具有最高访问优先级。在该 Session
内，所有针对同名表的查询和操作仅对临时表生效（创建物化视图除外）。
-:::
-
-## 适用场景
-
-临时表适用于以下数据处理场景：
-
-- **复杂 SQL 拆分**：将大型查询拆分为多个步骤，逐步落地中间结果，降低单条 SQL 的复杂度。
-- **中间结果暂存**：在 ETL、数据探查或报表开发中保存计算中间产物，避免重复计算。
-- **数据调试与验证**：将每一步的计算结果物化，便于查看和校对，提升可调试性。
-- **会话隔离的数据处理**：需要数据在会话内可见、会话结束自动回收的场景，避免遗留数据污染。
-
-## 用法
-
-### 创建临时表
-
-各种模型的表都可以被定义为临时表，无论是 Unique、Aggregate 还是 Duplicate 模型。可以在下列 SQL 中添加
`TEMPORARY` 关键字创建临时表：
-
-- [CREATE
TABLE](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md)
-- [CREATE TABLE AS
SELECT](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md)
-- [CREATE TABLE
LIKE](../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE.md)
-
-### 操作临时表
-
-临时表的其它用法基本和普通内表相同。除上述 `CREATE` 语句外，其它 DDL 及 DML 语句无需添加 `TEMPORARY` 关键字。
-
-## 使用限制
-
-- 临时表只能在 Internal Catalog 中创建。
-- 建表时 ENGINE 必须为 OLAP。
-- 不支持使用 Alter 语句修改临时表。
-- 由于临时性，不支持基于临时表创建视图和物化视图。
-- 不支持备份临时表，也不支持使用 Sync Job 同步临时表。
-- 不支持导出、Stream Load、Broker Load、S3 Load、Mysql Load、Routine Load。
-- 删除临时表时，不进回收站，直接彻底删除。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/overview.mdx
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/overview.mdx
index 826d58373d1..66c8f9ac418 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/overview.mdx
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/overview.mdx
@@ -233,8 +233,8 @@ Doris 中表名默认大小写敏感，最大长度为 64 字节。可通过以
<div className="cards-grid">
<GettingStartedCard
- title="临时表"
- description="将复杂 SQL 拆分为多步并暂存中间结果，便于调试与复用"
+ title="临时表（已弃用）"
+ description="已弃用，请勿在生产环境中使用临时表"
link="./temporary-table"
/>
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/temporary-table.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/temporary-table.md
index a829b4d924a..d5afc22ab8b 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/temporary-table.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/table-design/temporary-table.md
@@ -1,14 +1,14 @@
---
{
- "title": "临时表（实验功能）",
+ "title": "临时表（已弃用）",
"language": "zh-CN",
- "description": "Doris 临时表（Temporary Table）是会话级物化内表，用于拆分复杂 SQL
查询、保存中间计算结果，会话结束后自动删除，无需手动清理。"
+ "description": "已弃用：Doris 临时表（Temporary Table）是会话级物化内表，用于拆分复杂 SQL
查询、保存中间计算结果。"
}
---
-:::note
+:::caution 已弃用
-临时表是一个实验性质的功能。不推荐在生产环境使用。
+临时表功能已弃用。不推荐在生产环境中使用。
:::
<!-- 知识类型: 功能特性 -->
diff --git a/sidebars.ts b/sidebars.ts
index cdb908dc63d..64ecd7e7ba4 100644
--- a/sidebars.ts
+++ b/sidebars.ts
@@ -317,7 +317,6 @@ const sidebars: SidebarsConfig = {
},
'table-design/schema-change',
'table-design/auto-increment',
- 'table-design/temporary-table',
],
},
{
diff --git a/versioned_docs/version-4.x/table-design/overview.mdx
b/versioned_docs/version-4.x/table-design/overview.mdx
index 494cc61a700..4e5d9724aac 100644
--- a/versioned_docs/version-4.x/table-design/overview.mdx
+++ b/versioned_docs/version-4.x/table-design/overview.mdx
@@ -233,8 +233,8 @@ Table properties apply at the partition level. Modifying
table properties only t
<div className="cards-grid">
<GettingStartedCard
- title="Temporary Tables"
- description="Break complex SQL into multiple steps and stage intermediate
results for easier debugging and reuse"
+ title="Temporary Tables (Deprecated)"
+ description="Deprecated. Do not use temporary tables in production
environments"
link="./temporary-table"
/>
diff --git a/versioned_docs/version-4.x/table-design/temporary-table.md
b/versioned_docs/version-4.x/table-design/temporary-table.md
index b0c67782a10..da086a55baa 100644
--- a/versioned_docs/version-4.x/table-design/temporary-table.md
+++ b/versioned_docs/version-4.x/table-design/temporary-table.md
@@ -1,14 +1,14 @@
---
{
- "title": "Temporary Table (Experimental)",
+ "title": "Temporary Table (Deprecated)",
"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."
+ "description": "Deprecated: A Doris temporary table is a session-scoped
materialized internal table used to break down complex SQL queries and store
intermediate computation results."
}
---
-:::note
+:::caution Deprecated
-The temporary table is an experimental feature. It is not recommended for use
in a production environment.
+The temporary table feature is deprecated. It is not recommended for use in a
production environment.
:::
<!-- Knowledge type: Feature -->
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
