This is an automated email from the ASF dual-hosted git repository.
kassiez 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 ee9f8ba47da fix name SQL conflict error in point query docs (#1439)
ee9f8ba47da is described below
commit ee9f8ba47daa4e6170933d50b8b920aaf1e088c7
Author: Kang <[email protected]>
AuthorDate: Tue Dec 10 19:57:17 2024 +0800
fix name SQL conflict error in point query docs (#1439)
## Versions
- [x] dev
- [x] 3.0
- [x] 2.1
- [x] 2.0
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [ ] Checked by AI
- [ ] Test Cases Built
---
.../high-concurrent-point-query.md | 18 +++++++++---------
.../high-concurrent-point-query.md | 18 +++++++++---------
.../version-2.0/query/high-concurrent-point-query.md | 16 ++++++++--------
.../high-concurrent-point-query.md | 20 ++++++++++----------
.../high-concurrent-point-query.md | 20 ++++++++++----------
.../version-2.0/query/high-concurrent-point-query.md | 16 ++++++++--------
.../high-concurrent-point-query.md | 20 ++++++++++----------
.../high-concurrent-point-query.md | 18 +++++++++---------
8 files changed, 73 insertions(+), 73 deletions(-)
diff --git a/docs/query-acceleration/high-concurrent-point-query.md
b/docs/query-acceleration/high-concurrent-point-query.md
index 2d626436f5b..395174a38ef 100644
--- a/docs/query-acceleration/high-concurrent-point-query.md
+++ b/docs/query-acceleration/high-concurrent-point-query.md
@@ -50,7 +50,7 @@ The above row storage is used to enable the Merge-On-Write
strategy under the Un
```sql
CREATE TABLE `tbl_point_query` (
- `key` int(11) NULL,
+ `k1` int(11) NULL,
`v1` decimal(27, 9) NULL,
`v2` varchar(30) NULL,
`v3` varchar(30) NULL,
@@ -59,9 +59,9 @@ CREATE TABLE `tbl_point_query` (
`v6` float NULL,
`v7` datev2 NULL
) ENGINE=OLAP
-UNIQUE KEY(`key`)
+UNIQUE KEY(`k1`)
COMMENT 'OLAP'
-DISTRIBUTED BY HASH(`key)` BUCKETS 1
+DISTRIBUTED BY HASH(`k1)` BUCKETS 1
PROPERTIES (
"replication_allocation" = "tag.location.default: 1",
"enable_unique_key_merge_on_write" = "true",
@@ -79,10 +79,10 @@ PROPERTIES (
4. It only supports equality queries on the key column of a single table and
does not support joins or nested subqueries. The WHERE condition should consist
of the key column alone and be an equality comparison. It can be considered as
a type of key-value query.
-5. Enabling rowstore may lead to space expansion and occupy more disk space.
For scenarios where querying only specific columns is needed, starting from
Doris 2.1, it is recommended to use `"row_store_columns"="key,v1,v2"` to
specify certain columns for rowstore storage. Queries can then selectively
access these columns, for example:
+5. Enabling rowstore may lead to space expansion and occupy more disk space.
For scenarios where querying only specific columns is needed, starting from
Doris 2.1, it is recommended to use `"row_store_columns"="k1,v1,v2"` to specify
certain columns for rowstore storage. Queries can then selectively access these
columns, for example:
```sql
- SELECT `key`, v1, v2 FROM tbl_point_query WHERE key = 1
+ SELECT k1, v1, v2 FROM tbl_point_query WHERE k1 = 1
```
## Using `PreparedStatement`
@@ -99,7 +99,7 @@ In order to reduce CPU cost for parsing query SQL and SQL
expressions, we provid
```java
// use `?` for placement holders, readStatement should be reused
- PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where key = ?");
+ PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where k1 = ?");
...
readStatement.setInt(1,1234);
ResultSet resultSet = readStatement.executeQuery();
@@ -131,13 +131,13 @@ Doris has a page-level cache that stores data for a
specific column in each page
A: explain sql, when SHORT-CIRCUIT appears in the execution plan, it proves
that short path optimization is used
```sql
-mysql> explain select * from tbl_point_query where `key` = -2147481418 ;
+mysql> explain select * from tbl_point_query where k1 = -2147481418 ;
+-----------------------------------------------------------------------------------------------+
| Explain String(Old Planner)
|
+-----------------------------------------------------------------------------------------------+
| PLAN FRAGMENT 0
|
| OUTPUT EXPRS:
|
- | `test`.`tbl_point_query`.`key`
|
+ | `test`.`tbl_point_query`.`k1`
|
| `test`.`tbl_point_query`.`v1`
|
| `test`.`tbl_point_query`.`v2`
|
| `test`.`tbl_point_query`.`v3`
|
@@ -154,7 +154,7 @@ mysql> explain select * from tbl_point_query where `key` =
-2147481418 ;
|
|
| 0:VOlapScanNode
|
| TABLE: test.tbl_point_query(tbl_point_query), PREAGGREGATION: ON
|
- | PREDICATES: `key` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
+ | PREDICATES: `k1` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
| partitions=1/1 (tbl_point_query), tablets=1/1, tabletList=360065
|
| cardinality=9452868, avgRowSize=833.31323, numNodes=1
|
| pushAggOp=NONE
|
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/high-concurrent-point-query.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/high-concurrent-point-query.md
index 49e8ffa7db3..0e4a51f28a0 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/high-concurrent-point-query.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/query-acceleration/high-concurrent-point-query.md
@@ -47,7 +47,7 @@ Doris 基于列存格式引擎构建，在高并发服务场景中，用户总
```sql
CREATE TABLE `tbl_point_query` (
- `key` int(11) NULL,
+ `k1` int(11) NULL,
`v1` decimal(27, 9) NULL,
`v2` varchar(30) NULL,
`v3` varchar(30) NULL,
@@ -56,9 +56,9 @@ CREATE TABLE `tbl_point_query` (
`v6` float NULL,
`v7` datev2 NULL
) ENGINE=OLAP
-UNIQUE KEY(`key`)
+UNIQUE KEY(`k1`)
COMMENT 'OLAP'
-DISTRIBUTED BY HASH(`key`) BUCKETS 1
+DISTRIBUTED BY HASH(`k1`) BUCKETS 1
PROPERTIES (
"replication_allocation" = "tag.location.default: 1",
"enable_unique_key_merge_on_write" = "true",
@@ -71,7 +71,7 @@ PROPERTIES (
1. `enable_unique_key_merge_on_write`应该被开启，存储引擎需要根据主键来快速点查
-2. 当条件只包含主键时，如`select * from tbl_point_query where key = 123`，类似的查询会走短路径来优化查询
+2. 当条件只包含主键时，如`select * from tbl_point_query where k1 = 123`，类似的查询会走短路径来优化查询
3. `light_schema_change`应该被开启，因为主键点查的优化依赖了轻量级 Schema Change 中的`column unique
id`来定位列
@@ -80,7 +80,7 @@ PROPERTIES (
5. 开启行存会导致空间膨胀，占用更多的磁盘空间，如果只需要查询部分列，在 Doris 2.1
后建议使用`"row_store_columns"="key,v1,v2"` 类似的方式指定部份列作为行存，查询的时候只查询这部份列，例如
```sql
- SELECT `key`, v1, v2 FROM tbl_point_query WHERE key = 1
+ SELECT k1, v1, v2 FROM tbl_point_query WHERE k1 = 1
```
## 使用 PreparedStatement
@@ -97,7 +97,7 @@ PROPERTIES (
```java
// use `?` for placement holders, readStatement should be reused
- PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where key = ?");
+ PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where k1 = ?");
...
readStatement.setInt(1,1234);
ResultSet resultSet = readStatement.executeQuery();
@@ -130,13 +130,13 @@ Doris 中有针对 Page 级别的 Cache，每个 Page 中存的是某一列的
A：explain sql，当执行计划中出现 SHORT-CIRCUIT，证明使用了短路径优化
```sql
-mysql> explain select * from tbl_point_query where `key` = -2147481418 ;
+mysql> explain select * from tbl_point_query where k1 = -2147481418 ;
+-----------------------------------------------------------------------------------------------+
| Explain String(Old Planner)
|
+-----------------------------------------------------------------------------------------------+
| PLAN FRAGMENT 0
|
| OUTPUT EXPRS:
|
-| `test`.`tbl_point_query`.`key`
|
+| `test`.`tbl_point_query`.`k1`
|
| `test`.`tbl_point_query`.`v1`
|
| `test`.`tbl_point_query`.`v2`
|
| `test`.`tbl_point_query`.`v3`
|
@@ -153,7 +153,7 @@ mysql> explain select * from tbl_point_query where `key` =
-2147481418 ;
|
|
| 0:VOlapScanNode
|
| TABLE: test.tbl_point_query(tbl_point_query), PREAGGREGATION: ON
|
-| PREDICATES: `key` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
+| PREDICATES: `k1` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
| partitions=1/1 (tbl_point_query), tablets=1/1, tabletList=360065
|
| cardinality=9452868, avgRowSize=833.31323, numNodes=1
|
| pushAggOp=NONE
|
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/query/high-concurrent-point-query.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/query/high-concurrent-point-query.md
index b55fdbe50b7..3466253c7ef 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/query/high-concurrent-point-query.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/query/high-concurrent-point-query.md
@@ -48,7 +48,7 @@ Doris 基于列存格式引擎构建，在高并发服务场景中，用户总
```sql
CREATE TABLE `tbl_point_query` (
- `key` int(11) NULL,
+ `k1` int(11) NULL,
`v1` decimal(27, 9) NULL,
`v2` varchar(30) NULL,
`v3` varchar(30) NULL,
@@ -57,9 +57,9 @@ CREATE TABLE `tbl_point_query` (
`v6` float NULL,
`v7` datev2 NULL
) ENGINE=OLAP
-UNIQUE KEY(`key`)
+UNIQUE KEY(`k1`)
COMMENT 'OLAP'
-DISTRIBUTED BY HASH(`key`) BUCKETS 1
+DISTRIBUTED BY HASH(`k1`) BUCKETS 1
PROPERTIES (
"replication_allocation" = "tag.location.default: 1",
"enable_unique_key_merge_on_write" = "true",
@@ -71,7 +71,7 @@ PROPERTIES (
**注意：**
1. `enable_unique_key_merge_on_write`应该被开启，存储引擎需要根据主键来快速点查
-2. 当条件只包含主键时，如`select * from tbl_point_query where key = 123`，类似的查询会走短路径来优化查询
+2. 当条件只包含主键时，如`select * from tbl_point_query where k1 = 123`，类似的查询会走短路径来优化查询
3. `light_schema_change`应该被开启，因为主键点查的优化依赖了轻量级 Schema Change 中的`column unique
id`来定位列
@@ -91,7 +91,7 @@ url = jdbc:mysql://127.0.0.1:9030/ycsb?useServerPrepStmts=true
```java
// use `?` for placement holders, readStatement should be reused
-PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where key = ?");
+PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where k1 = ?");
...
readStatement.setInt(1,1234);
ResultSet resultSet = readStatement.executeQuery();
@@ -124,13 +124,13 @@ Doris 中有针对 Page 级别的 Cache，每个 Page 中存的是某一列的
A：explain sql，当执行计划中出现 SHORT-CIRCUIT，证明使用了短路径优化
```sql
-mysql> explain select * from tbl_point_query where `key` = -2147481418 ;
+mysql> explain select * from tbl_point_query where k1 = -2147481418 ;
+-----------------------------------------------------------------------------------------------+
| Explain String(Old Planner)
|
+-----------------------------------------------------------------------------------------------+
| PLAN FRAGMENT 0
|
| OUTPUT EXPRS:
|
-| `test`.`tbl_point_query`.`key`
|
+| `test`.`tbl_point_query`.`k1`
|
| `test`.`tbl_point_query`.`v1`
|
| `test`.`tbl_point_query`.`v2`
|
| `test`.`tbl_point_query`.`v3`
|
@@ -147,7 +147,7 @@ mysql> explain select * from tbl_point_query where `key` =
-2147481418 ;
|
|
| 0:VOlapScanNode
|
| TABLE: test.tbl_point_query(tbl_point_query), PREAGGREGATION: ON
|
-| PREDICATES: `key` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
+| PREDICATES: `k1` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
| partitions=1/1 (tbl_point_query), tablets=1/1, tabletList=360065
|
| cardinality=9452868, avgRowSize=833.31323, numNodes=1
|
| pushAggOp=NONE
|
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/high-concurrent-point-query.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/high-concurrent-point-query.md
index 49e8ffa7db3..fad5f84fdd0 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/high-concurrent-point-query.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/query-acceleration/high-concurrent-point-query.md
@@ -47,7 +47,7 @@ Doris 基于列存格式引擎构建，在高并发服务场景中，用户总
```sql
CREATE TABLE `tbl_point_query` (
- `key` int(11) NULL,
+ `k1` int(11) NULL,
`v1` decimal(27, 9) NULL,
`v2` varchar(30) NULL,
`v3` varchar(30) NULL,
@@ -56,9 +56,9 @@ CREATE TABLE `tbl_point_query` (
`v6` float NULL,
`v7` datev2 NULL
) ENGINE=OLAP
-UNIQUE KEY(`key`)
+UNIQUE KEY(`k1`)
COMMENT 'OLAP'
-DISTRIBUTED BY HASH(`key`) BUCKETS 1
+DISTRIBUTED BY HASH(`k1`) BUCKETS 1
PROPERTIES (
"replication_allocation" = "tag.location.default: 1",
"enable_unique_key_merge_on_write" = "true",
@@ -71,16 +71,16 @@ PROPERTIES (
1. `enable_unique_key_merge_on_write`应该被开启，存储引擎需要根据主键来快速点查
-2. 当条件只包含主键时，如`select * from tbl_point_query where key = 123`，类似的查询会走短路径来优化查询
+2. 当条件只包含主键时，如`select * from tbl_point_query where k1 = 123`，类似的查询会走短路径来优化查询
3. `light_schema_change`应该被开启，因为主键点查的优化依赖了轻量级 Schema Change 中的`column unique
id`来定位列
4. 只支持单表 key 列等值查询不支持 join、嵌套子查询， **where 条件里需要有且仅有 key 列的等值**，可以认为是一种 key
value 查询
-5. 开启行存会导致空间膨胀，占用更多的磁盘空间，如果只需要查询部分列，在 Doris 2.1
后建议使用`"row_store_columns"="key,v1,v2"` 类似的方式指定部份列作为行存，查询的时候只查询这部份列，例如
+5. 开启行存会导致空间膨胀，占用更多的磁盘空间，如果只需要查询部分列，在 Doris 2.1
后建议使用`"row_store_columns"="k1,v1,v2"` 类似的方式指定部份列作为行存，查询的时候只查询这部份列，例如
```sql
- SELECT `key`, v1, v2 FROM tbl_point_query WHERE key = 1
+ SELECT k1, v1, v2 FROM tbl_point_query WHERE k1 = 1
```
## 使用 PreparedStatement
@@ -97,7 +97,7 @@ PROPERTIES (
```java
// use `?` for placement holders, readStatement should be reused
- PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where key = ?");
+ PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where k1 = ?");
...
readStatement.setInt(1,1234);
ResultSet resultSet = readStatement.executeQuery();
@@ -130,13 +130,13 @@ Doris 中有针对 Page 级别的 Cache，每个 Page 中存的是某一列的
A：explain sql，当执行计划中出现 SHORT-CIRCUIT，证明使用了短路径优化
```sql
-mysql> explain select * from tbl_point_query where `key` = -2147481418 ;
+mysql> explain select * from tbl_point_query where k1 = -2147481418 ;
+-----------------------------------------------------------------------------------------------+
| Explain String(Old Planner)
|
+-----------------------------------------------------------------------------------------------+
| PLAN FRAGMENT 0
|
| OUTPUT EXPRS:
|
-| `test`.`tbl_point_query`.`key`
|
+| `test`.`tbl_point_query`.`k1`
|
| `test`.`tbl_point_query`.`v1`
|
| `test`.`tbl_point_query`.`v2`
|
| `test`.`tbl_point_query`.`v3`
|
@@ -153,7 +153,7 @@ mysql> explain select * from tbl_point_query where `key` =
-2147481418 ;
|
|
| 0:VOlapScanNode
|
| TABLE: test.tbl_point_query(tbl_point_query), PREAGGREGATION: ON
|
-| PREDICATES: `key` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
+| PREDICATES: `k1` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
| partitions=1/1 (tbl_point_query), tablets=1/1, tabletList=360065
|
| cardinality=9452868, avgRowSize=833.31323, numNodes=1
|
| pushAggOp=NONE
|
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/query-acceleration/high-concurrent-point-query.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/query-acceleration/high-concurrent-point-query.md
index ba106e510f5..a57eb8fcbcf 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/query-acceleration/high-concurrent-point-query.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/query-acceleration/high-concurrent-point-query.md
@@ -47,7 +47,7 @@ Doris 基于列存格式引擎构建，在高并发服务场景中，用户总
```sql
CREATE TABLE `tbl_point_query` (
- `key` int(11) NULL,
+ `k1` int(11) NULL,
`v1` decimal(27, 9) NULL,
`v2` varchar(30) NULL,
`v3` varchar(30) NULL,
@@ -56,9 +56,9 @@ CREATE TABLE `tbl_point_query` (
`v6` float NULL,
`v7` datev2 NULL
) ENGINE=OLAP
-UNIQUE KEY(`key`)
+UNIQUE KEY(`k1`)
COMMENT 'OLAP'
-DISTRIBUTED BY HASH(`key`) BUCKETS 1
+DISTRIBUTED BY HASH(`k1`) BUCKETS 1
PROPERTIES (
"replication_allocation" = "tag.location.default: 1",
"enable_unique_key_merge_on_write" = "true",
@@ -71,16 +71,16 @@ PROPERTIES (
1. `enable_unique_key_merge_on_write`应该被开启，存储引擎需要根据主键来快速点查
-2. 当条件只包含主键时，如`select * from tbl_point_query where key = 123`，类似的查询会走短路径来优化查询
+2. 当条件只包含主键时，如`select * from tbl_point_query where k1 = 123`，类似的查询会走短路径来优化查询
3. `light_schema_change`应该被开启，因为主键点查的优化依赖了轻量级 Schema Change 中的`column unique
id`来定位列
4. 只支持单表 key 列等值查询不支持 join、嵌套子查询， **where 条件里需要有且仅有 key 列的等值**，可以认为是一种 key
value 查询
-5. 开启行存会导致空间膨胀，占用更多的磁盘空间，如果只需要查询部分列，在 Doris 2.1
后建议使用`"row_store_columns"="key,v1,v2"` 类似的方式指定部份列作为行存，查询的时候只查询这部份列，例如
+5. 开启行存会导致空间膨胀，占用更多的磁盘空间，如果只需要查询部分列，在 Doris 2.1
后建议使用`"row_store_columns"="k1,v1,v2"` 类似的方式指定部份列作为行存，查询的时候只查询这部份列，例如
```sql
- SELECT `key`, v1, v2 FROM tbl_point_query WHERE key = 1
+ SELECT k1, v1, v2 FROM tbl_point_query WHERE k1 = 1
```
## 使用 PreparedStatement
@@ -97,7 +97,7 @@ PROPERTIES (
```java
// use `?` for placement holders, readStatement should be reused
- PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where key = ?");
+ PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where k1 = ?");
...
readStatement.setInt(1,1234);
ResultSet resultSet = readStatement.executeQuery();
@@ -130,13 +130,13 @@ Doris 中有针对 Page 级别的 Cache，每个 Page 中存的是某一列的
A：explain sql，当执行计划中出现 SHORT-CIRCUIT，证明使用了短路径优化
```sql
-mysql> explain select * from tbl_point_query where `key` = -2147481418 ;
+mysql> explain select * from tbl_point_query where k1 = -2147481418 ;
+-----------------------------------------------------------------------------------------------+
| Explain String(Old Planner)
|
+-----------------------------------------------------------------------------------------------+
| PLAN FRAGMENT 0
|
| OUTPUT EXPRS:
|
-| `test`.`tbl_point_query`.`key`
|
+| `test`.`tbl_point_query`.`k1`
|
| `test`.`tbl_point_query`.`v1`
|
| `test`.`tbl_point_query`.`v2`
|
| `test`.`tbl_point_query`.`v3`
|
@@ -153,7 +153,7 @@ mysql> explain select * from tbl_point_query where `key` =
-2147481418 ;
|
|
| 0:VOlapScanNode
|
| TABLE: test.tbl_point_query(tbl_point_query), PREAGGREGATION: ON
|
-| PREDICATES: `key` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
+| PREDICATES: `k1` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
| partitions=1/1 (tbl_point_query), tablets=1/1, tabletList=360065
|
| cardinality=9452868, avgRowSize=833.31323, numNodes=1
|
| pushAggOp=NONE
|
diff --git a/versioned_docs/version-2.0/query/high-concurrent-point-query.md
b/versioned_docs/version-2.0/query/high-concurrent-point-query.md
index f0dcebeee4e..64ae210f838 100644
--- a/versioned_docs/version-2.0/query/high-concurrent-point-query.md
+++ b/versioned_docs/version-2.0/query/high-concurrent-point-query.md
@@ -53,7 +53,7 @@ The above row storage is used to enable the Merge-On-Write
strategy under the Un
```sql
CREATE TABLE `tbl_point_query` (
- `key` int(11) NULL,
+ `k1` int(11) NULL,
`v1` decimal(27, 9) NULL,
`v2` varchar(30) NULL,
`v3` varchar(30) NULL,
@@ -62,9 +62,9 @@ CREATE TABLE `tbl_point_query` (
`v6` float NULL,
`v7` datev2 NULL
) ENGINE=OLAP
-UNIQUE KEY(`key`)
+UNIQUE KEY(`k1`)
COMMENT 'OLAP'
-DISTRIBUTED BY HASH(`key)` BUCKETS 1
+DISTRIBUTED BY HASH(`k1)` BUCKETS 1
PROPERTIES (
"replication_allocation" = "tag.location.default: 1",
"enable_unique_key_merge_on_write" = "true",
@@ -75,7 +75,7 @@ PROPERTIES (
**Note:**
1. `enable_unique_key_merge_on_write` should be enabled, since we need primary
key for quick point lookup in storage engine
-2. when condition only contains primary key like `select * from
tbl_point_query where key = 123`, such query will go through the short fast path
+2. when condition only contains primary key like `select * from
tbl_point_query where k1 = 123`, such query will go through the short fast path
3. `light_schema_change` should also been enabled since we rely on `column
unique id` of each column when doing a point query.
4. It only supports equality queries on the key column of a single table and
does not support joins or nested subqueries. The WHERE condition should consist
of the key column alone and be an equality comparison. It can be considered as
a type of key-value query.
@@ -94,7 +94,7 @@ url = jdbc:mysql://127.0.0.1:9030/ycsb?useServerPrepStmts=true
```java
// use `?` for placement holders, readStatement should be reused
-PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where key = ?");
+PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where k1 = ?");
...
readStatement.setInt(1,1234);
ResultSet resultSet = readStatement.executeQuery();
@@ -119,13 +119,13 @@ Doris has a page-level cache that stores data for a
specific column in each page
1. How to confirm that the configuration is correct and short path
optimization using concurrent enumeration is used
A: explain sql, when SHORT-CIRCUIT appears in the execution plan, it proves
that short path optimization is used
```sql
- mysql> explain select * from tbl_point_query where `key` = -2147481418 ;
+ mysql> explain select * from tbl_point_query where k1 = -2147481418 ;
+-----------------------------------------------------------------------------------------------+
| Explain String(Old Planner)
|
+-----------------------------------------------------------------------------------------------+
| PLAN FRAGMENT 0
|
| OUTPUT EXPRS:
|
- | `test`.`tbl_point_query`.`key`
|
+ | `test`.`tbl_point_query`.`k1`
|
| `test`.`tbl_point_query`.`v1`
|
| `test`.`tbl_point_query`.`v2`
|
| `test`.`tbl_point_query`.`v3`
|
@@ -142,7 +142,7 @@ Doris has a page-level cache that stores data for a
specific column in each page
|
|
| 0:VOlapScanNode
|
| TABLE: test.tbl_point_query(tbl_point_query), PREAGGREGATION:
ON |
- | PREDICATES: `key` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
+ | PREDICATES: `k1` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
| partitions=1/1 (tbl_point_query), tablets=1/1,
tabletList=360065 |
| cardinality=9452868, avgRowSize=833.31323, numNodes=1
|
| pushAggOp=NONE
|
diff --git
a/versioned_docs/version-2.1/query-acceleration/high-concurrent-point-query.md
b/versioned_docs/version-2.1/query-acceleration/high-concurrent-point-query.md
index 2d626436f5b..98fbde1ff8c 100644
---
a/versioned_docs/version-2.1/query-acceleration/high-concurrent-point-query.md
+++
b/versioned_docs/version-2.1/query-acceleration/high-concurrent-point-query.md
@@ -50,7 +50,7 @@ The above row storage is used to enable the Merge-On-Write
strategy under the Un
```sql
CREATE TABLE `tbl_point_query` (
- `key` int(11) NULL,
+ `k1` int(11) NULL,
`v1` decimal(27, 9) NULL,
`v2` varchar(30) NULL,
`v3` varchar(30) NULL,
@@ -59,9 +59,9 @@ CREATE TABLE `tbl_point_query` (
`v6` float NULL,
`v7` datev2 NULL
) ENGINE=OLAP
-UNIQUE KEY(`key`)
+UNIQUE KEY(`k1`)
COMMENT 'OLAP'
-DISTRIBUTED BY HASH(`key)` BUCKETS 1
+DISTRIBUTED BY HASH(`k1)` BUCKETS 1
PROPERTIES (
"replication_allocation" = "tag.location.default: 1",
"enable_unique_key_merge_on_write" = "true",
@@ -73,16 +73,16 @@ PROPERTIES (
**Note:**
1. `enable_unique_key_merge_on_write` should be enabled, since we need primary
key for quick point lookup in storage engine
-2. when condition only contains primary key like `select * from
tbl_point_query where key = 123`, such query will go through the short fast path
+2. when condition only contains primary key like `select * from
tbl_point_query where k1 = 123`, such query will go through the short fast path
3. `light_schema_change` should also been enabled since we rely on `column
unique id` of each column when doing a point query.
4. It only supports equality queries on the key column of a single table and
does not support joins or nested subqueries. The WHERE condition should consist
of the key column alone and be an equality comparison. It can be considered as
a type of key-value query.
-5. Enabling rowstore may lead to space expansion and occupy more disk space.
For scenarios where querying only specific columns is needed, starting from
Doris 2.1, it is recommended to use `"row_store_columns"="key,v1,v2"` to
specify certain columns for rowstore storage. Queries can then selectively
access these columns, for example:
+5. Enabling rowstore may lead to space expansion and occupy more disk space.
For scenarios where querying only specific columns is needed, starting from
Doris 2.1, it is recommended to use `"row_store_columns"="k1,v1,v2"` to specify
certain columns for rowstore storage. Queries can then selectively access these
columns, for example:
```sql
- SELECT `key`, v1, v2 FROM tbl_point_query WHERE key = 1
+ SELECT k1, v1, v2 FROM tbl_point_query WHERE k1 = 1
```
## Using `PreparedStatement`
@@ -99,7 +99,7 @@ In order to reduce CPU cost for parsing query SQL and SQL
expressions, we provid
```java
// use `?` for placement holders, readStatement should be reused
- PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where key = ?");
+ PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where k1 = ?");
...
readStatement.setInt(1,1234);
ResultSet resultSet = readStatement.executeQuery();
@@ -131,13 +131,13 @@ Doris has a page-level cache that stores data for a
specific column in each page
A: explain sql, when SHORT-CIRCUIT appears in the execution plan, it proves
that short path optimization is used
```sql
-mysql> explain select * from tbl_point_query where `key` = -2147481418 ;
+mysql> explain select * from tbl_point_query where k1 = -2147481418 ;
+-----------------------------------------------------------------------------------------------+
| Explain String(Old Planner)
|
+-----------------------------------------------------------------------------------------------+
| PLAN FRAGMENT 0
|
| OUTPUT EXPRS:
|
- | `test`.`tbl_point_query`.`key`
|
+ | `test`.`tbl_point_query`.`k1`
|
| `test`.`tbl_point_query`.`v1`
|
| `test`.`tbl_point_query`.`v2`
|
| `test`.`tbl_point_query`.`v3`
|
@@ -154,7 +154,7 @@ mysql> explain select * from tbl_point_query where `key` =
-2147481418 ;
|
|
| 0:VOlapScanNode
|
| TABLE: test.tbl_point_query(tbl_point_query), PREAGGREGATION: ON
|
- | PREDICATES: `key` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
+ | PREDICATES: `k1` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
| partitions=1/1 (tbl_point_query), tablets=1/1, tabletList=360065
|
| cardinality=9452868, avgRowSize=833.31323, numNodes=1
|
| pushAggOp=NONE
|
diff --git
a/versioned_docs/version-3.0/query-acceleration/high-concurrent-point-query.md
b/versioned_docs/version-3.0/query-acceleration/high-concurrent-point-query.md
index 2d626436f5b..cc5ba8a0075 100644
---
a/versioned_docs/version-3.0/query-acceleration/high-concurrent-point-query.md
+++
b/versioned_docs/version-3.0/query-acceleration/high-concurrent-point-query.md
@@ -50,7 +50,7 @@ The above row storage is used to enable the Merge-On-Write
strategy under the Un
```sql
CREATE TABLE `tbl_point_query` (
- `key` int(11) NULL,
+ `k1` int(11) NULL,
`v1` decimal(27, 9) NULL,
`v2` varchar(30) NULL,
`v3` varchar(30) NULL,
@@ -59,9 +59,9 @@ CREATE TABLE `tbl_point_query` (
`v6` float NULL,
`v7` datev2 NULL
) ENGINE=OLAP
-UNIQUE KEY(`key`)
+UNIQUE KEY(`k1`)
COMMENT 'OLAP'
-DISTRIBUTED BY HASH(`key)` BUCKETS 1
+DISTRIBUTED BY HASH(`k1)` BUCKETS 1
PROPERTIES (
"replication_allocation" = "tag.location.default: 1",
"enable_unique_key_merge_on_write" = "true",
@@ -73,7 +73,7 @@ PROPERTIES (
**Note:**
1. `enable_unique_key_merge_on_write` should be enabled, since we need primary
key for quick point lookup in storage engine
-2. when condition only contains primary key like `select * from
tbl_point_query where key = 123`, such query will go through the short fast path
+2. when condition only contains primary key like `select * from
tbl_point_query where k1 = 123`, such query will go through the short fast path
3. `light_schema_change` should also been enabled since we rely on `column
unique id` of each column when doing a point query.
@@ -82,7 +82,7 @@ PROPERTIES (
5. Enabling rowstore may lead to space expansion and occupy more disk space.
For scenarios where querying only specific columns is needed, starting from
Doris 2.1, it is recommended to use `"row_store_columns"="key,v1,v2"` to
specify certain columns for rowstore storage. Queries can then selectively
access these columns, for example:
```sql
- SELECT `key`, v1, v2 FROM tbl_point_query WHERE key = 1
+ SELECT k1, v1, v2 FROM tbl_point_query WHERE k1 = 1
```
## Using `PreparedStatement`
@@ -99,7 +99,7 @@ In order to reduce CPU cost for parsing query SQL and SQL
expressions, we provid
```java
// use `?` for placement holders, readStatement should be reused
- PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where key = ?");
+ PreparedStatement readStatement = conn.prepareStatement("select * from
tbl_point_query where k1 = ?");
...
readStatement.setInt(1,1234);
ResultSet resultSet = readStatement.executeQuery();
@@ -131,13 +131,13 @@ Doris has a page-level cache that stores data for a
specific column in each page
A: explain sql, when SHORT-CIRCUIT appears in the execution plan, it proves
that short path optimization is used
```sql
-mysql> explain select * from tbl_point_query where `key` = -2147481418 ;
+mysql> explain select * from tbl_point_query where k1 = -2147481418 ;
+-----------------------------------------------------------------------------------------------+
| Explain String(Old Planner)
|
+-----------------------------------------------------------------------------------------------+
| PLAN FRAGMENT 0
|
| OUTPUT EXPRS:
|
- | `test`.`tbl_point_query`.`key`
|
+ | `test`.`tbl_point_query`.`k1`
|
| `test`.`tbl_point_query`.`v1`
|
| `test`.`tbl_point_query`.`v2`
|
| `test`.`tbl_point_query`.`v3`
|
@@ -154,7 +154,7 @@ mysql> explain select * from tbl_point_query where `key` =
-2147481418 ;
|
|
| 0:VOlapScanNode
|
| TABLE: test.tbl_point_query(tbl_point_query), PREAGGREGATION: ON
|
- | PREDICATES: `key` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
+ | PREDICATES: `k1` = -2147481418 AND
`test`.`tbl_point_query`.`__DORIS_DELETE_SIGN__` = 0 |
| partitions=1/1 (tbl_point_query), tablets=1/1, tabletList=360065
|
| cardinality=9452868, avgRowSize=833.31323, numNodes=1
|
| pushAggOp=NONE
|
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
