diff --git a/docs/table-design/temporary-table.md b/docs/table-design/temporary-table.md index 3e1a75bc7df7b..77c2724e88d26 100644 --- a/docs/table-design/temporary-table.md +++ b/docs/table-design/temporary-table.md @@ -31,12 +31,12 @@ When handling complex data processing, saving intermediate calculation results a To address this issue, Doris introduces the concept of temporary tables. A temporary table is a materialized internal table that exists temporarily and is primarily different from internal tables in that it only exists in the session that created it. Its lifecycle is bound to the current session, and the temporary table will be automatically deleted when the session ends. Moreover, the visibility of a temporary table is restricted to the session in which it was created, meaning it is not visible to another session of the same user at the same time. -::: note +:::note Similar to internal tables, temporary tables must be created under a Database within the Internal Catalog. However, since temporary tables are session-based, their naming is not subject to uniqueness constraints. You can create temporary tables with the same name in different sessions or create temporary tables with the same names as other internal tables. If a temporary table and a non-temporary table with the same name exist simultaneously in the same Database, the temporary table has the highest access priority. Within that session, all queries and operations on the table with the same name will only affect the temporary table (except for creating materialized views). -:::: +::: ## Usage 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 index 49701302c42c6..6a978d07b1b5f 100644 --- 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 @@ -22,7 +22,7 @@ specific language governing permissions and limitations under the License. --> -:::note +:::info 备注 Supported since Doris version 2.1.7 / 3.0.2 ::: @@ -31,12 +31,12 @@ Supported since Doris version 2.1.7 / 3.0.2 为了解决上述问题，Doris 引入临时表类型。临时表是一种临时存在的物化内表，和内表的主要区别是其仅存在于创建它的 Session 中，它的生命周期和当前 Session 绑定。当会话结束时，在其中创建的临时表会被自动删除。从另一方面讲，临时表的可见性也仅在创建它的会话中，即使同一时间同一个用户的另一个会话也不可见。 -::: note +:::info 备注 与内表类似，临时表必须在 Internal Catalog 内的某个 Database 下创建。但由于临时表基于 Session，因此其命名不受唯一性约束。您可以在不同 Session 中创建同名临时表，或创建与其他内表同名的临时表。 如果同一 Database 中同时存在同名的临时表和非临时表，临时表具有最高访问优先级。在该 Session 内，所有针对同名表的查询和操作仅对临时表生效（除创建物化视图外）。 -:::: +::: ## 用法 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/temporary-table.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/temporary-table.md index 49701302c42c6..6a978d07b1b5f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/temporary-table.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/table-design/temporary-table.md @@ -22,7 +22,7 @@ specific language governing permissions and limitations under the License. --> -:::note +:::info 备注 Supported since Doris version 2.1.7 / 3.0.2 ::: @@ -31,12 +31,12 @@ Supported since Doris version 2.1.7 / 3.0.2 为了解决上述问题，Doris 引入临时表类型。临时表是一种临时存在的物化内表，和内表的主要区别是其仅存在于创建它的 Session 中，它的生命周期和当前 Session 绑定。当会话结束时，在其中创建的临时表会被自动删除。从另一方面讲，临时表的可见性也仅在创建它的会话中，即使同一时间同一个用户的另一个会话也不可见。 -::: note +:::info 备注 与内表类似，临时表必须在 Internal Catalog 内的某个 Database 下创建。但由于临时表基于 Session，因此其命名不受唯一性约束。您可以在不同 Session 中创建同名临时表，或创建与其他内表同名的临时表。 如果同一 Database 中同时存在同名的临时表和非临时表，临时表具有最高访问优先级。在该 Session 内，所有针对同名表的查询和操作仅对临时表生效（除创建物化视图外）。 -:::: +::: ## 用法 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/table-design/temporary-table.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/table-design/temporary-table.md index 49701302c42c6..6a978d07b1b5f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/table-design/temporary-table.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/table-design/temporary-table.md @@ -22,7 +22,7 @@ specific language governing permissions and limitations under the License. --> -:::note +:::info 备注 Supported since Doris version 2.1.7 / 3.0.2 ::: @@ -31,12 +31,12 @@ Supported since Doris version 2.1.7 / 3.0.2 为了解决上述问题，Doris 引入临时表类型。临时表是一种临时存在的物化内表，和内表的主要区别是其仅存在于创建它的 Session 中，它的生命周期和当前 Session 绑定。当会话结束时，在其中创建的临时表会被自动删除。从另一方面讲，临时表的可见性也仅在创建它的会话中，即使同一时间同一个用户的另一个会话也不可见。 -::: note +:::info 备注 与内表类似，临时表必须在 Internal Catalog 内的某个 Database 下创建。但由于临时表基于 Session，因此其命名不受唯一性约束。您可以在不同 Session 中创建同名临时表，或创建与其他内表同名的临时表。 如果同一 Database 中同时存在同名的临时表和非临时表，临时表具有最高访问优先级。在该 Session 内，所有针对同名表的查询和操作仅对临时表生效（除创建物化视图外）。 -:::: +::: ## 用法 diff --git a/versioned_docs/version-2.1/table-design/temporary-table.md b/versioned_docs/version-2.1/table-design/temporary-table.md index 3e1a75bc7df7b..77c2724e88d26 100644 --- a/versioned_docs/version-2.1/table-design/temporary-table.md +++ b/versioned_docs/version-2.1/table-design/temporary-table.md @@ -31,12 +31,12 @@ When handling complex data processing, saving intermediate calculation results a To address this issue, Doris introduces the concept of temporary tables. A temporary table is a materialized internal table that exists temporarily and is primarily different from internal tables in that it only exists in the session that created it. Its lifecycle is bound to the current session, and the temporary table will be automatically deleted when the session ends. Moreover, the visibility of a temporary table is restricted to the session in which it was created, meaning it is not visible to another session of the same user at the same time. -::: note +:::note Similar to internal tables, temporary tables must be created under a Database within the Internal Catalog. However, since temporary tables are session-based, their naming is not subject to uniqueness constraints. You can create temporary tables with the same name in different sessions or create temporary tables with the same names as other internal tables. If a temporary table and a non-temporary table with the same name exist simultaneously in the same Database, the temporary table has the highest access priority. Within that session, all queries and operations on the table with the same name will only affect the temporary table (except for creating materialized views). -:::: +::: ## Usage diff --git a/versioned_docs/version-3.0/table-design/temporary-table.md b/versioned_docs/version-3.0/table-design/temporary-table.md index 3e1a75bc7df7b..77c2724e88d26 100644 --- a/versioned_docs/version-3.0/table-design/temporary-table.md +++ b/versioned_docs/version-3.0/table-design/temporary-table.md @@ -31,12 +31,12 @@ When handling complex data processing, saving intermediate calculation results a To address this issue, Doris introduces the concept of temporary tables. A temporary table is a materialized internal table that exists temporarily and is primarily different from internal tables in that it only exists in the session that created it. Its lifecycle is bound to the current session, and the temporary table will be automatically deleted when the session ends. Moreover, the visibility of a temporary table is restricted to the session in which it was created, meaning it is not visible to another session of the same user at the same time. -::: note +:::note Similar to internal tables, temporary tables must be created under a Database within the Internal Catalog. However, since temporary tables are session-based, their naming is not subject to uniqueness constraints. You can create temporary tables with the same name in different sessions or create temporary tables with the same names as other internal tables. If a temporary table and a non-temporary table with the same name exist simultaneously in the same Database, the temporary table has the highest access priority. Within that session, all queries and operations on the table with the same name will only affect the temporary table (except for creating materialized views). -:::: +::: ## Usage