You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@doris.apache.org by da...@apache.org on 2023/04/21 14:31:04 UTC

[doris] branch master updated: [chore](doc) fix mv doc typo and cold heat separation (#18892)

This is an automated email from the ASF dual-hosted git repository.

dataroaring pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git


The following commit(s) were added to refs/heads/master by this push:
     new d56fed345e [chore](doc) fix mv doc typo and cold heat separation (#18892)
d56fed345e is described below

commit d56fed345e3fd79644ea1766a90e769d5f8b3ccb
Author: AlexYue <yj...@gmail.com>
AuthorDate: Fri Apr 21 22:30:56 2023 +0800

    [chore](doc) fix mv doc typo and cold heat separation (#18892)
---
 docs/en/docs/advanced/cold_hot_separation.md                      | 1 +
 .../Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW.md | 8 ++++----
 docs/zh-CN/docs/advanced/cold_hot_separation.md                   | 1 +
 .../Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW.md | 6 +++---
 4 files changed, 9 insertions(+), 7 deletions(-)

diff --git a/docs/en/docs/advanced/cold_hot_separation.md b/docs/en/docs/advanced/cold_hot_separation.md
index e88d0954f4..c1685faf5c 100644
--- a/docs/en/docs/advanced/cold_hot_separation.md
+++ b/docs/en/docs/advanced/cold_hot_separation.md
@@ -46,6 +46,7 @@ The cold and hot separation supports all doris functions, but only places some d
 - Remote object space recycling recycler. If the table and partition are deleted, or the space is wasted due to abnormal conditions in the cold and hot separation process, the recycler thread will periodically recycle, saving storage resources
 - Cache optimization, which caches the accessed cold data to be local, achieving the query performance of non cold and hot separation
 - Be thread pool optimization, distinguish whether the data source is local or object storage, and prevent the delay of reading objects from affecting query performance
+- newly created materialized view would inherit storage policy from it's base table's correspoding partition
 
 ## Storage policy
 
diff --git a/docs/en/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW.md b/docs/en/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW.md
index 911da28a42..9caa661d7a 100644
--- a/docs/en/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW.md
+++ b/docs/en/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW.md
@@ -115,8 +115,8 @@ attention:If the materialized view contains partitioned and distributed column
 1. Create a materialized view that contains only the columns of the original table (k1, k2)
 
    ```sql
-   create materialized view k1_k2 as
-   select k1, k2 from duplicate_table;
+   create materialized view k2_k1 as
+   select k2, k1 from duplicate_table;
    ````
 
    The schema of the materialized view is as follows, the materialized view contains only two columns k1, k2 without any aggregation
@@ -125,8 +125,8 @@ attention:If the materialized view contains partitioned and distributed column
    +-------+-------+--------+------+------+ ---------+-------+
    | IndexName | Field | Type | Null | Key | Default | Extra |
    +-------+-------+--------+------+------+ ---------+-------+
-   | k1_k2 | k1 | INT | Yes | true | N/A | |
-   | | k2 | INT | Yes | true | N/A | |
+   | k2_k1 | k2 | INT | Yes | true | N/A | |
+   | | k1 | INT | Yes | true | N/A | |
    +-------+-------+--------+------+------+ ---------+-------+
    ````
 
diff --git a/docs/zh-CN/docs/advanced/cold_hot_separation.md b/docs/zh-CN/docs/advanced/cold_hot_separation.md
index 8e13bee8dd..9aee8c7e1f 100644
--- a/docs/zh-CN/docs/advanced/cold_hot_separation.md
+++ b/docs/zh-CN/docs/advanced/cold_hot_separation.md
@@ -46,6 +46,7 @@ under the License.
 - 远程对象空间回收recycler,若表、分区被删除,或者冷热分离过程中异常情况产生的空间浪费,则会有recycler线程周期性的回收,节约存储资源
 - cache优化,将访问过的冷数据cache到be本地,达到非冷热分离的查询性能
 - be线程池优化,区分数据来源是本地还是对象存储,防止读取对象延时影响查询性能
+- 新建的物化视图也会继承相同partition的存储策略
 
 ## Storage policy的使用
 
diff --git a/docs/zh-CN/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW.md b/docs/zh-CN/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW.md
index 89ea2ae4e7..8f20884ccd 100644
--- a/docs/zh-CN/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW.md
+++ b/docs/zh-CN/docs/sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-MATERIALIZED-VIEW.md
@@ -116,7 +116,7 @@ properties("replication_num" = "1");
 
    ```sql
    create materialized view k1_k2 as
-   select k1, k2 from duplicate_table;
+   select k2, k1 from duplicate_table;
    ```
 
    物化视图的 schema 如下图,物化视图仅包含两列 k1, k2 且不带任何聚合
@@ -125,8 +125,8 @@ properties("replication_num" = "1");
    +-----------------+-------+--------+------+------+---------+-------+
    | IndexName       | Field | Type   | Null | Key  | Default | Extra |
    +-----------------+-------+--------+------+------+---------+-------+
-   | k1_k2           | k1    | INT    | Yes  | true | N/A     |       |
-   |                 | k2    | INT    | Yes  | true | N/A     |       |
+   | k2_k1           | k2    | INT    | Yes  | true | N/A     |       |
+   |                 | k1    | INT    | Yes  | true | N/A     |       |
    +-----------------+-------+--------+------+------+---------+-------+
    ```
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org