morrySnow commented on code in PR #29370:
URL: https://github.com/apache/doris/pull/29370#discussion_r1440090674
##########
docs/en/docs/query-acceleration/async-materialized-view/query-rewrite-summary-and-desc.md:
##########
@@ -0,0 +1,415 @@
+---
+{
+ "title": "Querying Asynchronous Materialized Views",
+ "language": "en"
+}
+---
+
+<!--
+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
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+## Overview
+
+Doris's asynchronous materialized views employ a structure based on the SPJG
(SELECT-PROJECT-JOIN-GROUP-BY) pattern
+for transparent rewriting algorithms. Doris can analyze the structural
information of the query SQL,
+automatically identify suitable materialized views, and attempt transparent
rewriting by expressing the
+query SQL using the materialized views. By utilizing precomputed materialized
view results,
+significant improvements in query performance and a reduction in computational
costs can be achieved.
+
+Using the three tables: lineitem, orders, and partsupp from TPC-H, let's
describe the capability of directly querying
+a materialized view and using the materialized view for transparent query
rewriting.
+```sql
+CREATE TABLE IF NOT EXISTS lineitem (
+ l_orderkey integer not null,
+ l_partkey integer not null,
+ l_suppkey integer not null,
+ l_linenumber integer not null,
+ l_quantity decimalv3(15,2) not null,
+ l_extendedprice decimalv3(15,2) not null,
+ l_discount decimalv3(15,2) not null,
+ l_tax decimalv3(15,2) not null,
+ l_returnflag char(1) not null,
+ l_linestatus char(1) not null,
+ l_shipdate date not null,
+ l_commitdate date not null,
+ l_receiptdate date not null,
+ l_shipinstruct char(25) not null,
+ l_shipmode char(10) not null,
+ l_comment varchar(44) not null
+ )
+ DUPLICATE KEY(l_orderkey, l_partkey, l_suppkey, l_linenumber)
+ PARTITION BY RANGE(l_shipdate)
+ (FROM ('2023-10-17') TO ('2023-10-20') INTERVAL 1 DAY)
+ DISTRIBUTED BY HASH(l_orderkey) BUCKETS 3
+ PROPERTIES ("replication_num" = "1");
+```
+```sql
+CREATE TABLE IF NOT EXISTS orders (
+ o_orderkey integer not null,
+ o_custkey integer not null,
+ o_orderstatus char(1) not null,
+ o_totalprice decimalv3(15,2) not null,
+ o_orderdate date not null,
+ o_orderpriority char(15) not null,
+ o_clerk char(15) not null,
+ o_shippriority integer not null,
+ o_comment varchar(79) not null
+ )
+ DUPLICATE KEY(o_orderkey, o_custkey)
+ PARTITION BY RANGE(o_orderdate)(
+ FROM ('2023-10-17') TO ('2023-10-20') INTERVAL 1 DAY)
+ DISTRIBUTED BY HASH(o_orderkey) BUCKETS 3
+ PROPERTIES ("replication_num" = "1");
+```
+
+```sql
+ CREATE TABLE IF NOT EXISTS partsupp (
+ ps_partkey INTEGER NOT NULL,
+ ps_suppkey INTEGER NOT NULL,
+ ps_availqty INTEGER NOT NULL,
+ ps_supplycost DECIMALV3(15,2) NOT NULL,
+ ps_comment VARCHAR(199) NOT NULL
+ )
+ DUPLICATE KEY(ps_partkey, ps_suppkey)
+ DISTRIBUTED BY HASH(ps_partkey) BUCKETS 3
+ PROPERTIES (
+ "replication_num" = "1"
+ );
+```
+
+## Direct Query of Materialized View
+A materialized view can be considered as a table and can be queried just like
a regular table.
+
+The syntax for defining a materialized view, details can be found in
+[CREATE-ASYNC-MATERIALIZED-VIEW](../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md)
+
+Materialized view definition:
+```sql
+CREATE MATERIALIZED VIEW mv1
+BUILD IMMEDIATE REFRESH AUTO ON SCHEDULE EVERY 1 hour
+DISTRIBUTED BY RANDOM BUCKETS 12
+PROPERTIES ('replication_num' = '1')
+AS
+SELECT t1.l_linenumber,
+ o_custkey,
+ o_orderdate
+FROM (SELECT * FROM lineitem WHERE l_linenumber > 1) t1
+ LEFT OUTER JOIN orders
+ ON l_orderkey = o_orderkey;
+```
+
+Query statement:
+Direct queries can be performed on the materialized view with additional
filtering conditions and aggregations.
+
+```sql
+SELECT l_linenumber,
+ o_custkey
+FROM mv1
+WHERE l_linenumber > 1 and o_orderdate = '2023-12-31';
+```
+
+## Transparent Rewriting Capability
+### Join rewriting
+
+JOIN rewriting refers to the ability to transparently rewrite a query when the
tables used in the query and
+the materialized view are the same. This rewriting can occur either by joining
the materialized view
+and the query inside the JOIN clause or by placing conditions in the WHERE
clause outside of the JOIN.
+Additionally, under certain conditions, when the types of JOINs in the query
and the materialized view do not match,
+rewriting can still take place.
+
+**Case 1:**
+
+The following case can undergo transparent rewriting. The condition
`l_linenumber > 1` allows for pull-up,
+enabling transparent rewriting by expressing the query using the precomputed
results of the materialized view.
+
+Materialized view definition:
+```sql
+SELECT t1.l_linenumber,
+ o_custkey,
+ o_orderdate
+FROM (SELECT * FROM lineitem WHERE l_linenumber > 1) t1
+LEFT OUTER JOIN orders
+ON l_orderkey = o_orderkey;
+```
+Query statement:
+
+```sql
+SELECT l_linenumber,
+ o_custkey
+FROM lineitem
+LEFT OUTER JOIN orders
+ON l_orderkey = o_orderkey
+WHERE l_linenumber > 1 and o_orderdate = '2023-12-31';
+```
+
+**Case 2:**
+
+OIN Derivation (TODO)
Review Comment:
```suggestion
JOIN Derivation (Comming soon)
```
##########
docs/en/docs/query-acceleration/async-materialized-view/query-rewrite-summary-and-desc.md:
##########
@@ -0,0 +1,415 @@
+---
+{
+ "title": "Querying Asynchronous Materialized Views",
+ "language": "en"
+}
+---
+
+<!--
+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
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+## Overview
+
+Doris's asynchronous materialized views employ a structure based on the SPJG
(SELECT-PROJECT-JOIN-GROUP-BY) pattern
+for transparent rewriting algorithms. Doris can analyze the structural
information of the query SQL,
+automatically identify suitable materialized views, and attempt transparent
rewriting by expressing the
+query SQL using the materialized views. By utilizing precomputed materialized
view results,
+significant improvements in query performance and a reduction in computational
costs can be achieved.
+
+Using the three tables: lineitem, orders, and partsupp from TPC-H, let's
describe the capability of directly querying
+a materialized view and using the materialized view for transparent query
rewriting.
+```sql
+CREATE TABLE IF NOT EXISTS lineitem (
+ l_orderkey integer not null,
+ l_partkey integer not null,
+ l_suppkey integer not null,
+ l_linenumber integer not null,
+ l_quantity decimalv3(15,2) not null,
+ l_extendedprice decimalv3(15,2) not null,
+ l_discount decimalv3(15,2) not null,
+ l_tax decimalv3(15,2) not null,
+ l_returnflag char(1) not null,
+ l_linestatus char(1) not null,
+ l_shipdate date not null,
+ l_commitdate date not null,
+ l_receiptdate date not null,
+ l_shipinstruct char(25) not null,
+ l_shipmode char(10) not null,
+ l_comment varchar(44) not null
+ )
+ DUPLICATE KEY(l_orderkey, l_partkey, l_suppkey, l_linenumber)
+ PARTITION BY RANGE(l_shipdate)
+ (FROM ('2023-10-17') TO ('2023-10-20') INTERVAL 1 DAY)
+ DISTRIBUTED BY HASH(l_orderkey) BUCKETS 3
+ PROPERTIES ("replication_num" = "1");
+```
+```sql
+CREATE TABLE IF NOT EXISTS orders (
+ o_orderkey integer not null,
+ o_custkey integer not null,
+ o_orderstatus char(1) not null,
+ o_totalprice decimalv3(15,2) not null,
+ o_orderdate date not null,
+ o_orderpriority char(15) not null,
+ o_clerk char(15) not null,
+ o_shippriority integer not null,
+ o_comment varchar(79) not null
+ )
+ DUPLICATE KEY(o_orderkey, o_custkey)
+ PARTITION BY RANGE(o_orderdate)(
+ FROM ('2023-10-17') TO ('2023-10-20') INTERVAL 1 DAY)
+ DISTRIBUTED BY HASH(o_orderkey) BUCKETS 3
+ PROPERTIES ("replication_num" = "1");
+```
+
+```sql
+ CREATE TABLE IF NOT EXISTS partsupp (
+ ps_partkey INTEGER NOT NULL,
+ ps_suppkey INTEGER NOT NULL,
+ ps_availqty INTEGER NOT NULL,
+ ps_supplycost DECIMALV3(15,2) NOT NULL,
+ ps_comment VARCHAR(199) NOT NULL
+ )
+ DUPLICATE KEY(ps_partkey, ps_suppkey)
+ DISTRIBUTED BY HASH(ps_partkey) BUCKETS 3
+ PROPERTIES (
+ "replication_num" = "1"
+ );
+```
+
+## Direct Query of Materialized View
+A materialized view can be considered as a table and can be queried just like
a regular table.
+
+The syntax for defining a materialized view, details can be found in
+[CREATE-ASYNC-MATERIALIZED-VIEW](../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md)
+
+Materialized view definition:
+```sql
+CREATE MATERIALIZED VIEW mv1
+BUILD IMMEDIATE REFRESH AUTO ON SCHEDULE EVERY 1 hour
+DISTRIBUTED BY RANDOM BUCKETS 12
+PROPERTIES ('replication_num' = '1')
+AS
+SELECT t1.l_linenumber,
+ o_custkey,
+ o_orderdate
+FROM (SELECT * FROM lineitem WHERE l_linenumber > 1) t1
+ LEFT OUTER JOIN orders
+ ON l_orderkey = o_orderkey;
+```
+
+Query statement:
+Direct queries can be performed on the materialized view with additional
filtering conditions and aggregations.
+
+```sql
+SELECT l_linenumber,
+ o_custkey
+FROM mv1
+WHERE l_linenumber > 1 and o_orderdate = '2023-12-31';
+```
+
+## Transparent Rewriting Capability
+### Join rewriting
+
+JOIN rewriting refers to the ability to transparently rewrite a query when the
tables used in the query and
+the materialized view are the same. This rewriting can occur either by joining
the materialized view
+and the query inside the JOIN clause or by placing conditions in the WHERE
clause outside of the JOIN.
+Additionally, under certain conditions, when the types of JOINs in the query
and the materialized view do not match,
+rewriting can still take place.
+
+**Case 1:**
+
+The following case can undergo transparent rewriting. The condition
`l_linenumber > 1` allows for pull-up,
+enabling transparent rewriting by expressing the query using the precomputed
results of the materialized view.
+
+Materialized view definition:
+```sql
+SELECT t1.l_linenumber,
+ o_custkey,
+ o_orderdate
+FROM (SELECT * FROM lineitem WHERE l_linenumber > 1) t1
+LEFT OUTER JOIN orders
+ON l_orderkey = o_orderkey;
+```
+Query statement:
+
+```sql
+SELECT l_linenumber,
+ o_custkey
+FROM lineitem
+LEFT OUTER JOIN orders
+ON l_orderkey = o_orderkey
+WHERE l_linenumber > 1 and o_orderdate = '2023-12-31';
+```
+
+**Case 2:**
+
+OIN Derivation (TODO)
+When the types of JOINs in the query and the materialized view do not match,
but the materialized view can provide
+all the data required for the query, transparent rewriting can also occur by
compensating predicates above the JOIN.
+For example:
+
+Materialized view definition:
+```sql
+SELECT
+ l_shipdate, l_suppkey, o_orderdate
+ sum(o_totalprice) AS sum_total,
+ max(o_totalprice) AS max_total,
+ min(o_totalprice) AS min_total,
+ count(*) AS count_all,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS bitmap_union_basic
+FROM lineitem
+LEFT OUTER JOIN orders ON lineitem.l_orderkey = orders.o_orderkey AND
l_shipdate = o_orderdate
+GROUP BY
+l_shipdate,
+l_suppkey,
+o_orderdate;
+```
+
+Query statement:
+```sql
+SELECT
+ l_shipdate, l_suppkey, o_orderdate
+ sum(o_totalprice) AS sum_total,
+ max(o_totalprice) AS max_total,
+ min(o_totalprice) AS min_total,
+ count(*) AS count_all,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS bitmap_union_basic
+FROM lineitem
+INNER JOIN orders ON lineitem.l_orderkey = orders.o_orderkey AND l_shipdate =
o_orderdate
+WHERE o_orderdate = '2023-12-11' AND l_suppkey = 3
+GROUP BY
+l_shipdate,
+l_suppkey,
+o_orderdate;
+```
+
+### 聚合改写
Review Comment:
english
##########
docs/en/docs/query-acceleration/async-materialized-view/query-rewrite-summary-and-desc.md:
##########
@@ -0,0 +1,415 @@
+---
+{
+ "title": "Querying Asynchronous Materialized Views",
+ "language": "en"
+}
+---
+
+<!--
+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
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+## Overview
+
+Doris's asynchronous materialized views employ a structure based on the SPJG
(SELECT-PROJECT-JOIN-GROUP-BY) pattern
+for transparent rewriting algorithms. Doris can analyze the structural
information of the query SQL,
+automatically identify suitable materialized views, and attempt transparent
rewriting by expressing the
+query SQL using the materialized views. By utilizing precomputed materialized
view results,
+significant improvements in query performance and a reduction in computational
costs can be achieved.
+
+Using the three tables: lineitem, orders, and partsupp from TPC-H, let's
describe the capability of directly querying
+a materialized view and using the materialized view for transparent query
rewriting.
+```sql
+CREATE TABLE IF NOT EXISTS lineitem (
+ l_orderkey integer not null,
+ l_partkey integer not null,
+ l_suppkey integer not null,
+ l_linenumber integer not null,
+ l_quantity decimalv3(15,2) not null,
+ l_extendedprice decimalv3(15,2) not null,
+ l_discount decimalv3(15,2) not null,
+ l_tax decimalv3(15,2) not null,
+ l_returnflag char(1) not null,
+ l_linestatus char(1) not null,
+ l_shipdate date not null,
+ l_commitdate date not null,
+ l_receiptdate date not null,
+ l_shipinstruct char(25) not null,
+ l_shipmode char(10) not null,
+ l_comment varchar(44) not null
+ )
+ DUPLICATE KEY(l_orderkey, l_partkey, l_suppkey, l_linenumber)
+ PARTITION BY RANGE(l_shipdate)
+ (FROM ('2023-10-17') TO ('2023-10-20') INTERVAL 1 DAY)
+ DISTRIBUTED BY HASH(l_orderkey) BUCKETS 3
+ PROPERTIES ("replication_num" = "1");
+```
+```sql
+CREATE TABLE IF NOT EXISTS orders (
+ o_orderkey integer not null,
+ o_custkey integer not null,
+ o_orderstatus char(1) not null,
+ o_totalprice decimalv3(15,2) not null,
+ o_orderdate date not null,
+ o_orderpriority char(15) not null,
+ o_clerk char(15) not null,
+ o_shippriority integer not null,
+ o_comment varchar(79) not null
+ )
+ DUPLICATE KEY(o_orderkey, o_custkey)
+ PARTITION BY RANGE(o_orderdate)(
+ FROM ('2023-10-17') TO ('2023-10-20') INTERVAL 1 DAY)
+ DISTRIBUTED BY HASH(o_orderkey) BUCKETS 3
+ PROPERTIES ("replication_num" = "1");
+```
+
+```sql
+ CREATE TABLE IF NOT EXISTS partsupp (
+ ps_partkey INTEGER NOT NULL,
+ ps_suppkey INTEGER NOT NULL,
+ ps_availqty INTEGER NOT NULL,
+ ps_supplycost DECIMALV3(15,2) NOT NULL,
+ ps_comment VARCHAR(199) NOT NULL
+ )
+ DUPLICATE KEY(ps_partkey, ps_suppkey)
+ DISTRIBUTED BY HASH(ps_partkey) BUCKETS 3
+ PROPERTIES (
+ "replication_num" = "1"
+ );
+```
+
+## Direct Query of Materialized View
+A materialized view can be considered as a table and can be queried just like
a regular table.
+
+The syntax for defining a materialized view, details can be found in
+[CREATE-ASYNC-MATERIALIZED-VIEW](../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md)
+
+Materialized view definition:
+```sql
+CREATE MATERIALIZED VIEW mv1
+BUILD IMMEDIATE REFRESH AUTO ON SCHEDULE EVERY 1 hour
+DISTRIBUTED BY RANDOM BUCKETS 12
+PROPERTIES ('replication_num' = '1')
+AS
+SELECT t1.l_linenumber,
+ o_custkey,
+ o_orderdate
+FROM (SELECT * FROM lineitem WHERE l_linenumber > 1) t1
+ LEFT OUTER JOIN orders
+ ON l_orderkey = o_orderkey;
+```
+
+Query statement:
+Direct queries can be performed on the materialized view with additional
filtering conditions and aggregations.
+
+```sql
+SELECT l_linenumber,
+ o_custkey
+FROM mv1
+WHERE l_linenumber > 1 and o_orderdate = '2023-12-31';
+```
+
+## Transparent Rewriting Capability
+### Join rewriting
+
+JOIN rewriting refers to the ability to transparently rewrite a query when the
tables used in the query and
+the materialized view are the same. This rewriting can occur either by joining
the materialized view
+and the query inside the JOIN clause or by placing conditions in the WHERE
clause outside of the JOIN.
+Additionally, under certain conditions, when the types of JOINs in the query
and the materialized view do not match,
+rewriting can still take place.
+
+**Case 1:**
+
+The following case can undergo transparent rewriting. The condition
`l_linenumber > 1` allows for pull-up,
+enabling transparent rewriting by expressing the query using the precomputed
results of the materialized view.
+
+Materialized view definition:
+```sql
+SELECT t1.l_linenumber,
+ o_custkey,
+ o_orderdate
+FROM (SELECT * FROM lineitem WHERE l_linenumber > 1) t1
+LEFT OUTER JOIN orders
+ON l_orderkey = o_orderkey;
+```
+Query statement:
+
+```sql
+SELECT l_linenumber,
+ o_custkey
+FROM lineitem
+LEFT OUTER JOIN orders
+ON l_orderkey = o_orderkey
+WHERE l_linenumber > 1 and o_orderdate = '2023-12-31';
+```
+
+**Case 2:**
+
+OIN Derivation (TODO)
+When the types of JOINs in the query and the materialized view do not match,
but the materialized view can provide
+all the data required for the query, transparent rewriting can also occur by
compensating predicates above the JOIN.
+For example:
+
+Materialized view definition:
+```sql
+SELECT
+ l_shipdate, l_suppkey, o_orderdate
+ sum(o_totalprice) AS sum_total,
+ max(o_totalprice) AS max_total,
+ min(o_totalprice) AS min_total,
+ count(*) AS count_all,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS bitmap_union_basic
+FROM lineitem
+LEFT OUTER JOIN orders ON lineitem.l_orderkey = orders.o_orderkey AND
l_shipdate = o_orderdate
+GROUP BY
+l_shipdate,
+l_suppkey,
+o_orderdate;
+```
+
+Query statement:
+```sql
+SELECT
+ l_shipdate, l_suppkey, o_orderdate
+ sum(o_totalprice) AS sum_total,
+ max(o_totalprice) AS max_total,
+ min(o_totalprice) AS min_total,
+ count(*) AS count_all,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS bitmap_union_basic
+FROM lineitem
+INNER JOIN orders ON lineitem.l_orderkey = orders.o_orderkey AND l_shipdate =
o_orderdate
+WHERE o_orderdate = '2023-12-11' AND l_suppkey = 3
+GROUP BY
+l_shipdate,
+l_suppkey,
+o_orderdate;
+```
+
+### 聚合改写
+
+**Case 1**
+
+The following case can undergo transparent rewriting. The query and the
materialized view use consistent dimensions
+for aggregation, allowing the use of fields from the dimensions to filter
results. The query will attempt to use the
+expressions after SELECT in the materialized view.
+
+Materialized view definition:
+
+```sql
+SELECT
+ o_shippriority, o_comment,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS cnt_1,
+ count(distinct CASE WHEN O_SHIPPRIORITY > 2 AND o_orderkey IN (2) THEN
o_custkey ELSE null END) AS cnt_2,
+ sum(o_totalprice),
+ max(o_totalprice),
+ min(o_totalprice),
+ count(*)
+FROM orders
+GROUP BY
+o_shippriority,
+o_comment;
+```
+
+Query statement:
+
+```sql
+SELECT
+ o_shippriority, o_comment,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS cnt_1,
+ count(distinct CASE WHEN O_SHIPPRIORITY > 2 AND o_orderkey IN (2) THEN
o_custkey ELSE null END) AS cnt_2,
+ sum(o_totalprice),
+ max(o_totalprice),
+ min(o_totalprice),
+ count(*)
+FROM orders
+WHERE o_shippriority in (1, 2)
+GROUP BY
+o_shippriority,
+o_comment;
+```
+
+**Case 2**
+
+The following query can undergo transparent rewriting. The query and the
materialized view use inconsistent
+dimensions for aggregation, where the dimensions used by the materialized view
include those used by the query.
+The query will attempt to roll up using the functions after SELECT, such as
the materialized view's
+bitmap_union will eventually roll up into bitmap_union_count, maintaining
consistency with the semantics of
+the count(distinct) in the query.
+
+Materialized view definition:
+
+```sql
+SELECT
+ l_shipdate, o_orderdate, l_partkey, l_suppkey,
+ sum(o_totalprice) AS sum_total,
+ max(o_totalprice) AS max_total,
+ min(o_totalprice) AS min_total,
+ count(*) AS count_all,
+ bitmap_union(to_bitmap(CASE WHEN o_shippriority > 1 AND o_orderkey IN (1,
3) THEN o_custkey ELSE null END)) AS bitmap_union_basic
+FROM lineitem
+LEFT OUTER JOIN orders ON lineitem.l_orderkey = orders.o_orderkey AND
l_shipdate = o_orderdate
+GROUP BY
+l_shipdate,
+o_orderdate,
+l_partkey,
+l_suppkey;
+```
+
+Query statement:
+
+```sql
+SELECT
+ l_shipdate, l_suppkey,
+ sum(o_totalprice) AS sum_total,
+ max(o_totalprice) AS max_total,
+ min(o_totalprice) AS min_total,
+ count(*) AS count_all,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS bitmap_union_basic
+FROM lineitem
+LEFT OUTER JOIN orders ON lineitem.l_orderkey = orders.o_orderkey AND
l_shipdate = o_orderdate
+WHERE o_orderdate = '2023-12-11' AND l_partkey = 3
+GROUP BY
+l_shipdate,
+l_suppkey;
+```
+
+Temporary support for the aggregation roll-up functions is as follows:
+
+| Functions in Queries | Functions in Materialized Views | Aggregation
Functions After Rewriting |
+|----------------------|----------------------------------|---------------------------------------|
+| max | max | max
|
+| min | min | min
|
+| sum | sum | sum
|
+| count | count | sum
|
+| count(distinct ) | bitmap_union | bitmap_union_count
|
+| bitmap_union | bitmap_union | bitmap_union
|
+| bitmap_union_count | bitmap_union | bitmap_union_count
|
+
+## Query partial Transparent Rewriting (TODO)
+When the number of tables in the materialized view is greater than the query,
if the materialized view
+satisfies the conditions for JOIN elimination for tables more than the query,
transparent rewriting can also occur.
+For example:
+
+**Case 1**
+
+Materialized view definition:
+
+```sql
+ SELECT
+ l_linenumber,
+ o_custkey,
+ ps_availqty
+ FROM lineitem
+ LEFT OUTER JOIN orders ON L_ORDERKEY = O_ORDERKEY
+ LEFT OUTER JOIN partsupp ON l_partkey = ps_partkey
+ AND l_suppkey = ps_suppkey;
+```
+
+Query statement:
+```sql
+ SELECT
+ l_linenumber,
+ o_custkey,
+ ps_availqty
+ FROM lineitem
+ LEFT OUTER JOIN orders ON L_ORDERKEY = O_ORDERKEY;
+```
+
+## Union Rewriting (TODO)
Review Comment:
```suggestion
## Union Rewriting (Coming soon)
```
##########
docs/en/docs/query-acceleration/async-materialized-view/query-rewrite-summary-and-desc.md:
##########
@@ -0,0 +1,415 @@
+---
+{
+ "title": "Querying Asynchronous Materialized Views",
+ "language": "en"
+}
+---
+
+<!--
+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
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+## Overview
+
+Doris's asynchronous materialized views employ a structure based on the SPJG
(SELECT-PROJECT-JOIN-GROUP-BY) pattern
+for transparent rewriting algorithms. Doris can analyze the structural
information of the query SQL,
+automatically identify suitable materialized views, and attempt transparent
rewriting by expressing the
+query SQL using the materialized views. By utilizing precomputed materialized
view results,
+significant improvements in query performance and a reduction in computational
costs can be achieved.
+
+Using the three tables: lineitem, orders, and partsupp from TPC-H, let's
describe the capability of directly querying
+a materialized view and using the materialized view for transparent query
rewriting.
+```sql
+CREATE TABLE IF NOT EXISTS lineitem (
+ l_orderkey integer not null,
+ l_partkey integer not null,
+ l_suppkey integer not null,
+ l_linenumber integer not null,
+ l_quantity decimalv3(15,2) not null,
+ l_extendedprice decimalv3(15,2) not null,
+ l_discount decimalv3(15,2) not null,
+ l_tax decimalv3(15,2) not null,
+ l_returnflag char(1) not null,
+ l_linestatus char(1) not null,
+ l_shipdate date not null,
+ l_commitdate date not null,
+ l_receiptdate date not null,
+ l_shipinstruct char(25) not null,
+ l_shipmode char(10) not null,
+ l_comment varchar(44) not null
+ )
+ DUPLICATE KEY(l_orderkey, l_partkey, l_suppkey, l_linenumber)
+ PARTITION BY RANGE(l_shipdate)
+ (FROM ('2023-10-17') TO ('2023-10-20') INTERVAL 1 DAY)
+ DISTRIBUTED BY HASH(l_orderkey) BUCKETS 3
+ PROPERTIES ("replication_num" = "1");
+```
+```sql
+CREATE TABLE IF NOT EXISTS orders (
+ o_orderkey integer not null,
+ o_custkey integer not null,
+ o_orderstatus char(1) not null,
+ o_totalprice decimalv3(15,2) not null,
+ o_orderdate date not null,
+ o_orderpriority char(15) not null,
+ o_clerk char(15) not null,
+ o_shippriority integer not null,
+ o_comment varchar(79) not null
+ )
+ DUPLICATE KEY(o_orderkey, o_custkey)
+ PARTITION BY RANGE(o_orderdate)(
+ FROM ('2023-10-17') TO ('2023-10-20') INTERVAL 1 DAY)
+ DISTRIBUTED BY HASH(o_orderkey) BUCKETS 3
+ PROPERTIES ("replication_num" = "1");
+```
+
+```sql
+ CREATE TABLE IF NOT EXISTS partsupp (
+ ps_partkey INTEGER NOT NULL,
+ ps_suppkey INTEGER NOT NULL,
+ ps_availqty INTEGER NOT NULL,
+ ps_supplycost DECIMALV3(15,2) NOT NULL,
+ ps_comment VARCHAR(199) NOT NULL
+ )
+ DUPLICATE KEY(ps_partkey, ps_suppkey)
+ DISTRIBUTED BY HASH(ps_partkey) BUCKETS 3
+ PROPERTIES (
+ "replication_num" = "1"
+ );
+```
+
+## Direct Query of Materialized View
+A materialized view can be considered as a table and can be queried just like
a regular table.
+
+The syntax for defining a materialized view, details can be found in
+[CREATE-ASYNC-MATERIALIZED-VIEW](../../sql-manual/sql-reference/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW.md)
+
+Materialized view definition:
+```sql
+CREATE MATERIALIZED VIEW mv1
+BUILD IMMEDIATE REFRESH AUTO ON SCHEDULE EVERY 1 hour
+DISTRIBUTED BY RANDOM BUCKETS 12
+PROPERTIES ('replication_num' = '1')
+AS
+SELECT t1.l_linenumber,
+ o_custkey,
+ o_orderdate
+FROM (SELECT * FROM lineitem WHERE l_linenumber > 1) t1
+ LEFT OUTER JOIN orders
+ ON l_orderkey = o_orderkey;
+```
+
+Query statement:
+Direct queries can be performed on the materialized view with additional
filtering conditions and aggregations.
+
+```sql
+SELECT l_linenumber,
+ o_custkey
+FROM mv1
+WHERE l_linenumber > 1 and o_orderdate = '2023-12-31';
+```
+
+## Transparent Rewriting Capability
+### Join rewriting
+
+JOIN rewriting refers to the ability to transparently rewrite a query when the
tables used in the query and
+the materialized view are the same. This rewriting can occur either by joining
the materialized view
+and the query inside the JOIN clause or by placing conditions in the WHERE
clause outside of the JOIN.
+Additionally, under certain conditions, when the types of JOINs in the query
and the materialized view do not match,
+rewriting can still take place.
+
+**Case 1:**
+
+The following case can undergo transparent rewriting. The condition
`l_linenumber > 1` allows for pull-up,
+enabling transparent rewriting by expressing the query using the precomputed
results of the materialized view.
+
+Materialized view definition:
+```sql
+SELECT t1.l_linenumber,
+ o_custkey,
+ o_orderdate
+FROM (SELECT * FROM lineitem WHERE l_linenumber > 1) t1
+LEFT OUTER JOIN orders
+ON l_orderkey = o_orderkey;
+```
+Query statement:
+
+```sql
+SELECT l_linenumber,
+ o_custkey
+FROM lineitem
+LEFT OUTER JOIN orders
+ON l_orderkey = o_orderkey
+WHERE l_linenumber > 1 and o_orderdate = '2023-12-31';
+```
+
+**Case 2:**
+
+OIN Derivation (TODO)
+When the types of JOINs in the query and the materialized view do not match,
but the materialized view can provide
+all the data required for the query, transparent rewriting can also occur by
compensating predicates above the JOIN.
+For example:
+
+Materialized view definition:
+```sql
+SELECT
+ l_shipdate, l_suppkey, o_orderdate
+ sum(o_totalprice) AS sum_total,
+ max(o_totalprice) AS max_total,
+ min(o_totalprice) AS min_total,
+ count(*) AS count_all,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS bitmap_union_basic
+FROM lineitem
+LEFT OUTER JOIN orders ON lineitem.l_orderkey = orders.o_orderkey AND
l_shipdate = o_orderdate
+GROUP BY
+l_shipdate,
+l_suppkey,
+o_orderdate;
+```
+
+Query statement:
+```sql
+SELECT
+ l_shipdate, l_suppkey, o_orderdate
+ sum(o_totalprice) AS sum_total,
+ max(o_totalprice) AS max_total,
+ min(o_totalprice) AS min_total,
+ count(*) AS count_all,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS bitmap_union_basic
+FROM lineitem
+INNER JOIN orders ON lineitem.l_orderkey = orders.o_orderkey AND l_shipdate =
o_orderdate
+WHERE o_orderdate = '2023-12-11' AND l_suppkey = 3
+GROUP BY
+l_shipdate,
+l_suppkey,
+o_orderdate;
+```
+
+### 聚合改写
+
+**Case 1**
+
+The following case can undergo transparent rewriting. The query and the
materialized view use consistent dimensions
+for aggregation, allowing the use of fields from the dimensions to filter
results. The query will attempt to use the
+expressions after SELECT in the materialized view.
+
+Materialized view definition:
+
+```sql
+SELECT
+ o_shippriority, o_comment,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS cnt_1,
+ count(distinct CASE WHEN O_SHIPPRIORITY > 2 AND o_orderkey IN (2) THEN
o_custkey ELSE null END) AS cnt_2,
+ sum(o_totalprice),
+ max(o_totalprice),
+ min(o_totalprice),
+ count(*)
+FROM orders
+GROUP BY
+o_shippriority,
+o_comment;
+```
+
+Query statement:
+
+```sql
+SELECT
+ o_shippriority, o_comment,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS cnt_1,
+ count(distinct CASE WHEN O_SHIPPRIORITY > 2 AND o_orderkey IN (2) THEN
o_custkey ELSE null END) AS cnt_2,
+ sum(o_totalprice),
+ max(o_totalprice),
+ min(o_totalprice),
+ count(*)
+FROM orders
+WHERE o_shippriority in (1, 2)
+GROUP BY
+o_shippriority,
+o_comment;
+```
+
+**Case 2**
+
+The following query can undergo transparent rewriting. The query and the
materialized view use inconsistent
+dimensions for aggregation, where the dimensions used by the materialized view
include those used by the query.
+The query will attempt to roll up using the functions after SELECT, such as
the materialized view's
+bitmap_union will eventually roll up into bitmap_union_count, maintaining
consistency with the semantics of
+the count(distinct) in the query.
+
+Materialized view definition:
+
+```sql
+SELECT
+ l_shipdate, o_orderdate, l_partkey, l_suppkey,
+ sum(o_totalprice) AS sum_total,
+ max(o_totalprice) AS max_total,
+ min(o_totalprice) AS min_total,
+ count(*) AS count_all,
+ bitmap_union(to_bitmap(CASE WHEN o_shippriority > 1 AND o_orderkey IN (1,
3) THEN o_custkey ELSE null END)) AS bitmap_union_basic
+FROM lineitem
+LEFT OUTER JOIN orders ON lineitem.l_orderkey = orders.o_orderkey AND
l_shipdate = o_orderdate
+GROUP BY
+l_shipdate,
+o_orderdate,
+l_partkey,
+l_suppkey;
+```
+
+Query statement:
+
+```sql
+SELECT
+ l_shipdate, l_suppkey,
+ sum(o_totalprice) AS sum_total,
+ max(o_totalprice) AS max_total,
+ min(o_totalprice) AS min_total,
+ count(*) AS count_all,
+ count(distinct CASE WHEN o_shippriority > 1 AND o_orderkey IN (1, 3) THEN
o_custkey ELSE null END) AS bitmap_union_basic
+FROM lineitem
+LEFT OUTER JOIN orders ON lineitem.l_orderkey = orders.o_orderkey AND
l_shipdate = o_orderdate
+WHERE o_orderdate = '2023-12-11' AND l_partkey = 3
+GROUP BY
+l_shipdate,
+l_suppkey;
+```
+
+Temporary support for the aggregation roll-up functions is as follows:
+
+| Functions in Queries | Functions in Materialized Views | Aggregation
Functions After Rewriting |
+|----------------------|----------------------------------|---------------------------------------|
+| max | max | max
|
+| min | min | min
|
+| sum | sum | sum
|
+| count | count | sum
|
+| count(distinct ) | bitmap_union | bitmap_union_count
|
+| bitmap_union | bitmap_union | bitmap_union
|
+| bitmap_union_count | bitmap_union | bitmap_union_count
|
+
+## Query partial Transparent Rewriting (TODO)
Review Comment:
```suggestion
## Query partial Transparent Rewriting (Coming soon)
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
