You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by pa...@apache.org on 2022/07/14 06:08:46 UTC
[shardingsphere] branch master updated: Remove best practice (#19132)
This is an automated email from the ASF dual-hosted git repository.
panjuan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new c6ac3c20c9e Remove best practice (#19132)
c6ac3c20c9e is described below
commit c6ac3c20c9e69a044a22cf32eb2417c35bd9732c
Author: Liang Zhang <zh...@apache.org>
AuthorDate: Thu Jul 14 14:08:40 2022 +0800
Remove best practice (#19132)
---
docs/document/content/best-practices/_index.cn.md | 8 ---
docs/document/content/best-practices/_index.en.md | 8 ---
docs/document/content/best-practices/encrypt.cn.md | 68 ------------------
docs/document/content/best-practices/encrypt.en.md | 69 ------------------
.../best-practices/readwrite-splitting.cn.md | 74 -------------------
.../best-practices/readwrite-splitting.en.md | 74 -------------------
.../document/content/best-practices/sharding.cn.md | 83 ----------------------
.../document/content/best-practices/sharding.en.md | 83 ----------------------
.../content/best-practices/transaction.cn.md | 18 -----
.../content/best-practices/transaction.en.md | 19 -----
docs/document/content/downloads/_index.cn.md | 4 +-
docs/document/content/downloads/_index.en.md | 4 +-
docs/document/content/reference/_index.cn.md | 4 +-
docs/document/content/reference/_index.en.md | 4 +-
.../reference/api-change-history/_index.cn.md | 2 +-
.../reference/api-change-history/_index.en.md | 2 +-
.../content/reference/distsql/_index.cn.md | 2 +-
.../content/reference/distsql/_index.en.md | 2 +-
.../content/reference/encrypt/_index.cn.md | 2 +-
.../content/reference/encrypt/_index.en.md | 2 +-
docs/document/content/reference/faq/_index.cn.md | 2 +-
docs/document/content/reference/faq/_index.en.md | 2 +-
.../content/reference/management/_index.cn.md | 2 +-
.../content/reference/management/_index.en.md | 2 +-
.../content/reference/scaling/_index.cn.md | 2 +-
.../content/reference/scaling/_index.en.md | 2 +-
.../document/content/reference/shadow/_index.cn.md | 2 +-
.../document/content/reference/shadow/_index.en.md | 2 +-
.../content/reference/sharding/_index.cn.md | 2 +-
.../content/reference/sharding/_index.en.md | 2 +-
docs/document/content/reference/test/_index.cn.md | 2 +-
docs/document/content/reference/test/_index.en.md | 2 +-
.../content/reference/transaction/_index.cn.md | 2 +-
.../content/reference/transaction/_index.en.md | 2 +-
34 files changed, 28 insertions(+), 532 deletions(-)
diff --git a/docs/document/content/best-practices/_index.cn.md b/docs/document/content/best-practices/_index.cn.md
deleted file mode 100644
index baafde57acd..00000000000
--- a/docs/document/content/best-practices/_index.cn.md
+++ /dev/null
@@ -1,8 +0,0 @@
-+++
-pre = "<b>7. </b>"
-title = "最佳实践"
-weight = 7
-chapter = true
-+++
-
-本章节面向 Apache ShardingSphere 的用户，阐述各个功能的最佳实践。
\ No newline at end of file
diff --git a/docs/document/content/best-practices/_index.en.md b/docs/document/content/best-practices/_index.en.md
deleted file mode 100644
index e367336e151..00000000000
--- a/docs/document/content/best-practices/_index.en.md
+++ /dev/null
@@ -1,8 +0,0 @@
-+++
-pre = "<b>7. </b>"
-title = "Best Practices"
-weight = 7
-chapter = true
-+++
-
-This chapter is aimed at users of Apache ShardingSphere and describes best practices for each feature.
\ No newline at end of file
diff --git a/docs/document/content/best-practices/encrypt.cn.md b/docs/document/content/best-practices/encrypt.cn.md
deleted file mode 100644
index 5c9e54293dd..00000000000
--- a/docs/document/content/best-practices/encrypt.cn.md
+++ /dev/null
@@ -1,68 +0,0 @@
-+++
-pre = "<b>7.5. </b>"
-title = "数据加密"
-weight = 5
-chapter = true
-+++
-
-## 适用场景
-不论是新业务需要使用数据加密的功能，还是需要对已有业务进行改造满足加密需求，Apache ShardingSphere 都提供了一套完整的数据加密解决方案。用户可以通过如下实践进行学习了解。
-## 前提条件
-假设新业务上线，现在期望对用户的密码字段进行加密存储于数据库中，但同时系统要能够获取明文数据。
-## 数据规划
-由于用户期望对密码字段进行加密存储，但是系统又要能够获取明文字段，那么我们可以采用可逆算法 AES 对数据进行加密。因此我们可以采用如配置示例中所示的配置，对`t_user` 表进行加密，逻辑列名称为 `pwd`，也就是业务 SQL 中采用的字段名称，该字段映射到数据库中为 `pwd_cipher` 字段，对应的加密算法采用 AES。
-## 操作步骤
-1. 下载 ShardingSphere-proxy
-2. 采用如配置示例所示的加密配置
-3. 连接 proxy 后，创建 `t_user` 表
-``` sql
-## 可以通过 PREVIEW 语法查看真实创建表语法
-encrypt_db=> PREVIEW CREATE TABLE t_user (user_id INT NOT NULL, username VARCHAR(200), pwd VARCHAR(200) NOT NULL, PRIMARY KEY (user_id));
- data_source_name | actual_sql
-------------------+----------------------------------------------------------------------------------------------------------------------------
- ds_0 | CREATE TABLE t_user (user_id INT NOT NULL, username VARCHAR(200), pwd_cipher VARCHAR(200) NOT NULL, PRIMARY KEY (user_id))
-(1 row)
-CREATE TABLE t_user (user_id INT NOT NULL, username VARCHAR(200), pwd VARCHAR(200) NOT NULL, PRIMARY KEY (user_id));
-```
-4. 向 `t_user` 表中插入数据
-``` sql
-encrypt_db=> PREVIEW INSERT INTO t_user values (1,'ZHANGSAN','123456');
- data_source_name | actual_sql
-------------------+------------------------------------------------------------------------------------------------------
- ds_0 | INSERT INTO t_user(user_id, username, pwd_cipher) values (1, 'ZHANGSAN', 'MyOShk4kjRnds7CZfU5NCw==')
-(1 row)
-INSERT INTO t_user values (1,'ZHANGSAN','123456');
-```
-5. 查询 `t_user` 表
-``` sql
-encrypt_db=> PREVIEW SELECT * FROM t_user WHERE pwd = '123456';
- data_source_name | actual_sql
-------------------+------------------------------------------------------------------------------------------------------------------------------------------
- ds_0 | SELECT "t_user"."user_id", "t_user"."username", "t_user"."pwd_cipher" AS "pwd" FROM t_user WHERE pwd_cipher = 'MyOShk4kjRnds7CZfU5NCw=='
-(1 row)
-encrypt_db=> SELECT * FROM t_user WHERE pwd = '123456';
- user_id | username | pwd
----------+----------+--------
- 1 | ZHANGSAN | 123456
-(1 row)
-```
-
-## 配置示例
-config-encrypt.yaml
-``` yaml
-rules:
-- !ENCRYPT
- encryptors:
- aes_encryptor:
- type: AES
- props:
- aes-key-value: 123456abc
- tables:
- t_user:
- columns:
- pwd:
- cipherColumn: pwd_cipher
- encryptorName: aes_encryptor
-```
-## 相关参考
-[YAML 配置：数据加密](/cn/user-manual/shardingsphere-jdbc/yaml-config/rules/encrypt/)
\ No newline at end of file
diff --git a/docs/document/content/best-practices/encrypt.en.md b/docs/document/content/best-practices/encrypt.en.md
deleted file mode 100644
index cc3e4e2853d..00000000000
--- a/docs/document/content/best-practices/encrypt.en.md
+++ /dev/null
@@ -1,69 +0,0 @@
-+++
-pre = "<b>7.5. </b>"
-title = "Encryption"
-weight = 5
-chapter = true
-+++
-
-## Scenarios
-Whether a new business needs to use data encryption capabilities, or an existing business needs to be transformed to meet encryption needs, Apache ShardingSphere provides a complete set of data encryption solutions.
-## Prerequisites
-Assuming that the new service goes online, it is now expected that the user's password field will be encrypted and stored in the database, but at the same time, the system should be able to obtain plaintext data.
-## Data Planning
-Since the user expects the password field to be stored encrypted, but the system needs to be able to obtain the plaintext field, we can encrypt the data using the reversible algorithm AES.
-So we can encrypt the `t_user` table with the logical column name `pwd`, which is the field name in Business SQL, which maps to the 'pwd_cipher' field in the database, corresponding to AES, using the configuration shown in the configuration example.
-## Procedure
-1. Download ShardingSphere-proxy.
-2. Use the encryption configuration shown in the configuration example.
-3. After the proxy is connected, create the `t_user` table.
-``` sql
-## You can view the real creation table syntax through the PREVIEW syntax.
-encrypt_db=> PREVIEW CREATE TABLE t_user (user_id INT NOT NULL, username VARCHAR(200), pwd VARCHAR(200) NOT NULL, PRIMARY KEY (user_id));
- data_source_name | actual_sql
-------------------+----------------------------------------------------------------------------------------------------------------------------
- ds_0 | CREATE TABLE t_user (user_id INT NOT NULL, username VARCHAR(200), pwd_cipher VARCHAR(200) NOT NULL, PRIMARY KEY (user_id))
-(1 row)
-CREATE TABLE t_user (user_id INT NOT NULL, username VARCHAR(200), pwd VARCHAR(200) NOT NULL, PRIMARY KEY (user_id));
-```
-4. Insert data into the `t_user` table.
-``` sql
-encrypt_db=> PREVIEW INSERT INTO t_user values (1,'ZHANGSAN','123456');
- data_source_name | actual_sql
-------------------+------------------------------------------------------------------------------------------------------
- ds_0 | INSERT INTO t_user(user_id, username, pwd_cipher) values (1, 'ZHANGSAN', 'MyOShk4kjRnds7CZfU5NCw==')
-(1 row)
-INSERT INTO t_user values (1,'ZHANGSAN','123456');
-```
-5. Query `t_user` table.
-``` sql
-encrypt_db=> PREVIEW SELECT * FROM t_user WHERE pwd = '123456';
- data_source_name | actual_sql
-------------------+------------------------------------------------------------------------------------------------------------------------------------------
- ds_0 | SELECT "t_user"."user_id", "t_user"."username", "t_user"."pwd_cipher" AS "pwd" FROM t_user WHERE pwd_cipher = 'MyOShk4kjRnds7CZfU5NCw=='
-(1 row)
-encrypt_db=> SELECT * FROM t_user WHERE pwd = '123456';
- user_id | username | pwd
----------+----------+--------
- 1 | ZHANGSAN | 123456
-(1 row)
-```
-
-## Sample
-config-encrypt.yaml
-``` yaml
-rules:
-- !ENCRYPT
- encryptors:
- aes_encryptor:
- type: AES
- props:
- aes-key-value: 123456abc
- tables:
- t_user:
- columns:
- pwd:
- cipherColumn: pwd_cipher
- encryptorName: aes_encryptor
-```
-## Related References
-[YAML Configuration: Encryption](/en/user-manual/shardingsphere-jdbc/yaml-config/rules/encrypt/)
\ No newline at end of file
diff --git a/docs/document/content/best-practices/readwrite-splitting.cn.md b/docs/document/content/best-practices/readwrite-splitting.cn.md
deleted file mode 100644
index 6db06339327..00000000000
--- a/docs/document/content/best-practices/readwrite-splitting.cn.md
+++ /dev/null
@@ -1,74 +0,0 @@
-+++
-pre = "<b>7.3. </b>"
-title = "读写分离"
-weight = 3
-chapter = true
-+++
-
-## 适用场景
-适用于一主多从的数据库架构，主库负责数据的写入、修改、删除等事务性操作，从库负责查询操作。
-另外 Apache ShardingSphere 的读写分离功能提供了多种负载均衡策略。
-## 前提条件
-假设用户有一主二从的数据库架构，另外用户期望两个从库能够承担不同比重的负载。
-## 数据规划
-我们将采用读写分离配置，并且针对两个从库采用 `WEIGHT` 的负载均衡策略，让两个从库承担不同的负载。
-## 操作步骤
-1. 下载 ShardingSphere-proxy
-2. 采用如配置示例所示的读写分离配置
-3. 连接 proxy 后，创建 `t_order` 表
-``` sql
-## 可以通过 PREVIEW 语法查看真实创建表语法，可以看到路由结果都是指向了 write_ds
-readwrite_splitting_db=> PREVIEW CREATE TABLE t_order (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id));
- data_source_name | actual_sql
-------------------+---------------------------------------------------------------------------------------------------------------------
- write_ds | CREATE TABLE t_order (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id))
-(1 row)
-CREATE TABLE t_order (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id));
-```
-4. 向 `t_order` 表中插入数据
-``` sql
-readwrite_splitting_db=> PREVIEW INSERT INTO t_order values (1, 1,'OK');
- data_source_name | actual_sql
-------------------+----------------------------------------
- write_ds | INSERT INTO t_order values (1, 1,'OK')
-(1 row)
-INSERT INTO t_order values (1, 1,'OK')
-```
-5. 查询 `t_order` 表
-``` sql
-## 多次查询路由到不同从库
-readwrite_splitting_db=> PREVIEW SELECT * FROM t_order;
- data_source_name | actual_sql
-------------------+-----------------------
- read_ds_1 | SELECT * FROM t_order
-(1 row)
-
-readwrite_splitting_db=> PREVIEW SELECT * FROM t_order;
- data_source_name | actual_sql
-------------------+-----------------------
- read_ds_0 | SELECT * FROM t_order
-(1 row)
-```
-
-## 配置示例
-config-encrypt.yaml
-```yaml
-rules:
-- !READWRITE_SPLITTING
- dataSources:
- readwrite_ds:
- staticStrategy:
- writeDataSourceName: write_ds
- readDataSourceNames:
- - read_ds_0
- - read_ds_1
- loadBalancerName: weight_lb
- loadBalancers:
- weight_lb:
- type: WEIGHT
- props:
- read_ds_0: 2
- read_ds_1: 1
-```
-## 相关参考
-[YAML 配置：读写分离](/cn/user-manual/shardingsphere-jdbc/yaml-config/rules/readwrite-splitting/)
\ No newline at end of file
diff --git a/docs/document/content/best-practices/readwrite-splitting.en.md b/docs/document/content/best-practices/readwrite-splitting.en.md
deleted file mode 100644
index 34dccb1f779..00000000000
--- a/docs/document/content/best-practices/readwrite-splitting.en.md
+++ /dev/null
@@ -1,74 +0,0 @@
-+++
-pre = "<b>7.3. </b>"
-title = "Readwrite-splitting"
-weight = 3
-chapter = true
-+++
-
-## Scenarios
-Suitable for a one-primary and multi-secondary database architecture. The primary database is responsible for transactional operations such as writing, modifying, and deleting data, and the secondary database is responsible for query operations.
-Apache ShardingSphere's read/write splitting feature provides a variety of load balancing strategies.
-## Prerequisites
-Suppose the user has a database architecture of one primary and two secondary databases, and the user expects the two secondary databases to be able to bear different proportions of load.
-## Data Planning
-We will adopt a read/write splitting configuration and a load balancing strategy of `WEIGHT` for both secondary databases, so that the two secondary databases bear different loads.
-## Procedure
-1. Download ShardingSphere-proxy.
-2. Use the read/write splitting configuration shown in the configuration example.
-3. After the proxy is connected, create the `t_order` table.
-``` sql
-## You can view the actual creation table syntax through the PREVIEW syntax, and you can see that the routing results all point to the write_ds
-readwrite_splitting_db=> PREVIEW CREATE TABLE t_order (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id));
- data_source_name | actual_sql
-------------------+---------------------------------------------------------------------------------------------------------------------
- write_ds | CREATE TABLE t_order (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id))
-(1 row)
-CREATE TABLE t_order (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id));
-```
-4. Inserts data into the `t_order` table.
-``` sql
-readwrite_splitting_db=> PREVIEW INSERT INTO t_order values (1, 1,'OK');
- data_source_name | actual_sql
-------------------+----------------------------------------
- write_ds | INSERT INTO t_order values (1, 1,'OK')
-(1 row)
-INSERT INTO t_order values (1, 1,'OK')
-```
-5. Query `t_order` table.
-``` sql
-## Multiple queries are routed to different secondary databases.
-readwrite_splitting_db=> PREVIEW SELECT * FROM t_order;
- data_source_name | actual_sql
-------------------+-----------------------
- read_ds_1 | SELECT * FROM t_order
-(1 row)
-
-readwrite_splitting_db=> PREVIEW SELECT * FROM t_order;
- data_source_name | actual_sql
-------------------+-----------------------
- read_ds_0 | SELECT * FROM t_order
-(1 row)
-```
-
-## Sample
-config-encrypt.yaml
-```yaml
-rules:
-- !READWRITE_SPLITTING
- dataSources:
- readwrite_ds:
- staticStrategy:
- writeDataSourceName: write_ds
- readDataSourceNames:
- - read_ds_0
- - read_ds_1
- loadBalancerName: weight_lb
- loadBalancers:
- weight_lb:
- type: WEIGHT
- props:
- read_ds_0: 2
- read_ds_1: 1
-```
-## Related References
-[YAML Configuration: Readwrite-splitting](/en/user-manual/shardingsphere-jdbc/yaml-config/rules/readwrite-splitting/)
\ No newline at end of file
diff --git a/docs/document/content/best-practices/sharding.cn.md b/docs/document/content/best-practices/sharding.cn.md
deleted file mode 100644
index 6e59470772e..00000000000
--- a/docs/document/content/best-practices/sharding.cn.md
+++ /dev/null
@@ -1,83 +0,0 @@
-+++
-pre = "<b>7.1. </b>"
-title = "数据分片"
-weight = 1
-chapter = true
-+++
-
-## 适用场景
-适用于将单一节点的数据水平拆分存储至多个数据节点，并且期望业务 SQL 不做改造，依然可以针对单一存储节点书写的场景。
-## 前提条件
-假设用户期望对 `t_order` 表进行水平拆分至两个数据库实例共 4 张表，并且要求拆分后 SQL 依然针对 `t_order` 表书写。
-## 数据规划
-我们计划按照 `user_id % 2` 进行分库， `order_id % 2` 进行分表。
-## 操作步骤
-1. 下载 ShardingSphere-proxy
-2. 按照配置示例所示，配置 proxy 的分片功能，然后启动 proxy。
-3. 连接 proxy 后，创建 `t_order` 表
-``` sql
-## 可以通过 PREVIEW 语法查看真实创建表语法
-sharding_db=> PREVIEW CREATE TABLE t_order (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id));
- data_source_name | actual_sql
-------------------+-----------------------------------------------------------------------------------------------------------------------
- ds_1 | CREATE TABLE t_order_0 (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id))
- ds_1 | CREATE TABLE t_order_1 (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id))
- ds_0 | CREATE TABLE t_order_0 (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id))
- ds_0 | CREATE TABLE t_order_1 (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id))
-(4 rows)
-CREATE TABLE t_order (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id));
-```
-4. 向 `t_order` 表中插入数据
-``` sql
-sharding_db=> PREVIEW INSERT INTO t_order values (1, 1,'OK'),(2, 2, 'OK');
- data_source_name | actual_sql
-------------------+-------------------------------------------
- ds_1 | INSERT INTO t_order_1 values (1, 1, 'OK')
- ds_0 | INSERT INTO t_order_0 values (2, 2, 'OK')
-(2 rows)
-INSERT INTO t_order values (1, 1,'OK'),(2, 2, 'OK');
-```
-5. 查询 `t_order` 表
-``` sql
-sharding_db=> PREVIEW SELECT * FROM t_order;
- data_source_name | actual_sql
-------------------+-----------------------------------------------------------
- ds_0 | SELECT * FROM t_order_0 UNION ALL SELECT * FROM t_order_1
- ds_1 | SELECT * FROM t_order_0 UNION ALL SELECT * FROM t_order_1
-(2 rows)
-
-sharding_db=> PREVIEW SELECT * FROM t_order WHERE user_id = 1 and order_id = 1;
- data_source_name | actual_sql
-------------------+------------------------------------------------------------
- ds_1 | SELECT * FROM t_order_1 WHERE user_id = 1 and order_id = 1
-(1 row)
-```
-## 配置示例
-config-sharding.yaml
-``` yaml
-rules:
- - !SHARDING
- tables:
- t_order:
- actualDataNodes: ds_${0..1}.t_order_${0..1}
- databaseStrategy:
- standard:
- shardingColumn: user_id
- shardingAlgorithmName: database_inline
- tableStrategy:
- standard:
- shardingColumn: order_id
- shardingAlgorithmName: table_inline
-
- shardingAlgorithms:
- database_inline:
- type: INLINE
- props:
- algorithm-expression: ds_${user_id % 2}
- table_inline:
- type: INLINE
- props:
- algorithm-expression: t_order_${order_id % 2}
-```
-## 相关参考
-[YAML 配置：数据分片](/cn/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/)
\ No newline at end of file
diff --git a/docs/document/content/best-practices/sharding.en.md b/docs/document/content/best-practices/sharding.en.md
deleted file mode 100644
index df63ff1ebd6..00000000000
--- a/docs/document/content/best-practices/sharding.en.md
+++ /dev/null
@@ -1,83 +0,0 @@
-+++
-pre = "<b>7.1. </b>"
-title = "Sharding"
-weight = 1
-chapter = true
-+++
-
-## Scenarios
-Suitable for scenarios where the data level of a single node is split and stored in multiple data nodes, and it is expected that business SQL can still be written for a single storage node without modification.
-## Prerequisites
-Suppose you expect a horizontal split of the `t_order` table to a total of 4 tables in two DB instances, and you are required to write SQL against the `t_order` table after the split.
-## Data Planning
-We plan to divide the database according to `user_id % 2` and `order_id % 2` for the table.
-## Procedure
-1. Download ShardingSphere-proxy.
-2. Configure the sharding feature of the proxy as shown in the configuration example, and then start the proxy.
-3. After the proxy is connected, create the `t_order` table.
-``` sql
-## You can view the real creation table syntax through the PREVIEW syntax
-sharding_db=> PREVIEW CREATE TABLE t_order (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id));
- data_source_name | actual_sql
-------------------+-----------------------------------------------------------------------------------------------------------------------
- ds_1 | CREATE TABLE t_order_0 (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id))
- ds_1 | CREATE TABLE t_order_1 (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id))
- ds_0 | CREATE TABLE t_order_0 (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id))
- ds_0 | CREATE TABLE t_order_1 (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id))
-(4 rows)
-CREATE TABLE t_order (order_id INT NOT NULL, user_id INT NOT NULL, status VARCHAR(45) NULL, PRIMARY KEY (order_id));
-```
-4. Inserts data into the `t_order` table.
-``` sql
-sharding_db=> PREVIEW INSERT INTO t_order values (1, 1,'OK'),(2, 2, 'OK');
- data_source_name | actual_sql
-------------------+-------------------------------------------
- ds_1 | INSERT INTO t_order_1 values (1, 1, 'OK')
- ds_0 | INSERT INTO t_order_0 values (2, 2, 'OK')
-(2 rows)
-INSERT INTO t_order values (1, 1,'OK'),(2, 2, 'OK');
-```
-5. Query `t_order` table.
-``` sql
-sharding_db=> PREVIEW SELECT * FROM t_order;
- data_source_name | actual_sql
-------------------+-----------------------------------------------------------
- ds_0 | SELECT * FROM t_order_0 UNION ALL SELECT * FROM t_order_1
- ds_1 | SELECT * FROM t_order_0 UNION ALL SELECT * FROM t_order_1
-(2 rows)
-
-sharding_db=> PREVIEW SELECT * FROM t_order WHERE user_id = 1 and order_id = 1;
- data_source_name | actual_sql
-------------------+------------------------------------------------------------
- ds_1 | SELECT * FROM t_order_1 WHERE user_id = 1 and order_id = 1
-(1 row)
-```
-# Sample
-config-sharding.yaml
-``` yaml
-rules:
- - !SHARDING
- tables:
- t_order:
- actualDataNodes: ds_${0..1}.t_order_${0..1}
- databaseStrategy:
- standard:
- shardingColumn: user_id
- shardingAlgorithmName: database_inline
- tableStrategy:
- standard:
- shardingColumn: order_id
- shardingAlgorithmName: table_inline
-
- shardingAlgorithms:
- database_inline:
- type: INLINE
- props:
- algorithm-expression: ds_${user_id % 2}
- table_inline:
- type: INLINE
- props:
- algorithm-expression: t_order_${order_id % 2}
-```
-## Related References
-[YAML Configuration: Sharding](/en/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/)
\ No newline at end of file
diff --git a/docs/document/content/best-practices/transaction.cn.md b/docs/document/content/best-practices/transaction.cn.md
deleted file mode 100644
index de3ae02e930..00000000000
--- a/docs/document/content/best-practices/transaction.cn.md
+++ /dev/null
@@ -1,18 +0,0 @@
-+++
-pre = "<b>7.2. </b>"
-title = "分布式事务"
-weight = 2
-chapter = true
-+++
-
-## 适用场景
-
-Apache ShardingSphere 提供分布式场景下的事务语义，当有事务需求时，可以使用。ShardingSphere 提供了三种事务模式：LOCAL，XA，BASE，以应对不同的场景。
-
-- LOCAL：适用于对数据一致性要求不高的场景。
-- XA：提供了原子性的保证，保证了数据不丢，不保证快照读。适用于对一致性要求相对高，没有快照读要求的场景。在对一致性要求较高的场景，较好的选择是使用 XA 的 Narayana 实现。
-- BASE：在一致性和性能之间做了权衡，具体参考 Seata 官网。
-
-## 操作步骤
-
-参考 [ShardingSphere 使用 XA Narayana](/cn/user-manual/shardingsphere-jdbc/special-api/transaction/narayana/)
\ No newline at end of file
diff --git a/docs/document/content/best-practices/transaction.en.md b/docs/document/content/best-practices/transaction.en.md
deleted file mode 100644
index 5743688c56a..00000000000
--- a/docs/document/content/best-practices/transaction.en.md
+++ /dev/null
@@ -1,19 +0,0 @@
-+++
-pre = "<b>7.2. </b>"
-title = "Distributed Transaction"
-weight = 2
-chapter = true
-+++
-
-## Scenarios
-
-Apache ShardingSphere provides transaction semantics in distributed scenarios that can be used when transactional are required.
-ShardingSphere provides three transaction modes: LOCAL, XA, and BASE to address different scenarios.
-
-- LOCAL: Suitable for scenarios where data consistency requirements are not high.
-- XA: Provides atomicity guarantees, ensures that data is not lost, and snapshot reads are not guaranteed. Suitable for scenarios where consistency requirements are relatively high and there is no snapshot read requirement. In scenarios where consistency is required, a better choice is a Narayana implementation using XA.
-- BASE: A trade-off was made between consistency and performance, for details see Seata website.
-
-## Procedure
-
-See [ShardingSphere Using XA Narayana](/en/user-manual/shardingsphere-jdbc/special-api/transaction/narayana/)
\ No newline at end of file
diff --git a/docs/document/content/downloads/_index.cn.md b/docs/document/content/downloads/_index.cn.md
index 99e00c11946..775ca0b9f0b 100644
--- a/docs/document/content/downloads/_index.cn.md
+++ b/docs/document/content/downloads/_index.cn.md
@@ -1,7 +1,7 @@
+++
-pre = "<b>9. </b>"
+pre = "<b>8. </b>"
title = "下载"
-weight = 9
+weight = 8
chapter = true
extracss = true
+++
diff --git a/docs/document/content/downloads/_index.en.md b/docs/document/content/downloads/_index.en.md
index 8950da583f5..7fcef29dde4 100644
--- a/docs/document/content/downloads/_index.en.md
+++ b/docs/document/content/downloads/_index.en.md
@@ -1,7 +1,7 @@
+++
-pre = "<b>9. </b>"
+pre = "<b>8. </b>"
title = "Downloads"
-weight = 9
+weight = 8
chapter = true
extracss = true
+++
diff --git a/docs/document/content/reference/_index.cn.md b/docs/document/content/reference/_index.cn.md
index ce3bf579b77..7e2a550c6d0 100644
--- a/docs/document/content/reference/_index.cn.md
+++ b/docs/document/content/reference/_index.cn.md
@@ -1,7 +1,7 @@
+++
-pre = "<b>8. </b>"
+pre = "<b>7. </b>"
title = "技术参考"
-weight = 8
+weight = 7
chapter = true
+++
diff --git a/docs/document/content/reference/_index.en.md b/docs/document/content/reference/_index.en.md
index 7a1366182e2..b7a16bd64a7 100644
--- a/docs/document/content/reference/_index.en.md
+++ b/docs/document/content/reference/_index.en.md
@@ -1,7 +1,7 @@
+++
-pre = "<b>8. </b>"
+pre = "<b>7. </b>"
title = "Reference"
-weight = 8
+weight = 7
chapter = true
+++
diff --git a/docs/document/content/reference/api-change-history/_index.cn.md b/docs/document/content/reference/api-change-history/_index.cn.md
index 31e8436c8a5..a748a01eb1e 100644
--- a/docs/document/content/reference/api-change-history/_index.cn.md
+++ b/docs/document/content/reference/api-change-history/_index.cn.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.9. </b>"
+pre = "<b>7.9. </b>"
title = "API 变更历史"
weight = 9
chapter = true
diff --git a/docs/document/content/reference/api-change-history/_index.en.md b/docs/document/content/reference/api-change-history/_index.en.md
index 6f12183d819..fd962d0cf3e 100644
--- a/docs/document/content/reference/api-change-history/_index.en.md
+++ b/docs/document/content/reference/api-change-history/_index.en.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.9. </b>"
+pre = "<b>7.9. </b>"
title = "API Change Histories"
weight = 9
chapter = true
diff --git a/docs/document/content/reference/distsql/_index.cn.md b/docs/document/content/reference/distsql/_index.cn.md
index 0476394f572..ace849eb6e6 100644
--- a/docs/document/content/reference/distsql/_index.cn.md
+++ b/docs/document/content/reference/distsql/_index.cn.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.10. </b>"
+pre = "<b>7.10. </b>"
title = "DistSQL"
weight = 10
chapter = true
diff --git a/docs/document/content/reference/distsql/_index.en.md b/docs/document/content/reference/distsql/_index.en.md
index af436020b40..32d9ac9d139 100644
--- a/docs/document/content/reference/distsql/_index.en.md
+++ b/docs/document/content/reference/distsql/_index.en.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.10. </b>"
+pre = "<b>7.10. </b>"
title = "DistSQL"
weight = 10
chapter = true
diff --git a/docs/document/content/reference/encrypt/_index.cn.md b/docs/document/content/reference/encrypt/_index.cn.md
index d190e1ec7fb..2603ea70e66 100644
--- a/docs/document/content/reference/encrypt/_index.cn.md
+++ b/docs/document/content/reference/encrypt/_index.cn.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.5. </b>"
+pre = "<b>7.5. </b>"
title = "数据加密"
weight = 5
+++
diff --git a/docs/document/content/reference/encrypt/_index.en.md b/docs/document/content/reference/encrypt/_index.en.md
index 17a9a513676..752cd2bba03 100644
--- a/docs/document/content/reference/encrypt/_index.en.md
+++ b/docs/document/content/reference/encrypt/_index.en.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.5. </b>"
+pre = "<b>7.5. </b>"
title = "Encryption"
weight = 5
+++
diff --git a/docs/document/content/reference/faq/_index.cn.md b/docs/document/content/reference/faq/_index.cn.md
index 3a5e5a44317..16041f1d500 100644
--- a/docs/document/content/reference/faq/_index.cn.md
+++ b/docs/document/content/reference/faq/_index.cn.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.8. </b>"
+pre = "<b>7.8. </b>"
title = "FAQ"
weight = 8
chapter = true
diff --git a/docs/document/content/reference/faq/_index.en.md b/docs/document/content/reference/faq/_index.en.md
index be9ca30df35..8219ab782c4 100644
--- a/docs/document/content/reference/faq/_index.en.md
+++ b/docs/document/content/reference/faq/_index.en.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.8. </b>"
+pre = "<b>7.8. </b>"
title = "FAQ"
weight = 8
chapter = true
diff --git a/docs/document/content/reference/management/_index.cn.md b/docs/document/content/reference/management/_index.cn.md
index 5add7dc8eca..34ee38745bf 100644
--- a/docs/document/content/reference/management/_index.cn.md
+++ b/docs/document/content/reference/management/_index.cn.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.1. </b>"
+pre = "<b>7.1. </b>"
title = "管控"
weight = 1
+++
diff --git a/docs/document/content/reference/management/_index.en.md b/docs/document/content/reference/management/_index.en.md
index 0276e594dfe..88216ed4409 100644
--- a/docs/document/content/reference/management/_index.en.md
+++ b/docs/document/content/reference/management/_index.en.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.1. </b>"
+pre = "<b>7.1. </b>"
title = "Management"
weight = 1
+++
diff --git a/docs/document/content/reference/scaling/_index.cn.md b/docs/document/content/reference/scaling/_index.cn.md
index 2c935e56066..70e3af274af 100644
--- a/docs/document/content/reference/scaling/_index.cn.md
+++ b/docs/document/content/reference/scaling/_index.cn.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.4. </b>"
+pre = "<b>7.4. </b>"
title = "弹性伸缩"
weight = 4
+++
diff --git a/docs/document/content/reference/scaling/_index.en.md b/docs/document/content/reference/scaling/_index.en.md
index b182916c0bd..35e39278f66 100644
--- a/docs/document/content/reference/scaling/_index.en.md
+++ b/docs/document/content/reference/scaling/_index.en.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.4. </b>"
+pre = "<b>7.4. </b>"
title = "Scaling"
weight = 4
+++
diff --git a/docs/document/content/reference/shadow/_index.cn.md b/docs/document/content/reference/shadow/_index.cn.md
index e4a09d9e13a..9acb04ea384 100644
--- a/docs/document/content/reference/shadow/_index.cn.md
+++ b/docs/document/content/reference/shadow/_index.cn.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.6. </b>"
+pre = "<b>7.6. </b>"
title = "影子库"
weight = 6
+++
diff --git a/docs/document/content/reference/shadow/_index.en.md b/docs/document/content/reference/shadow/_index.en.md
index 9e2404b197f..51f6028efee 100644
--- a/docs/document/content/reference/shadow/_index.en.md
+++ b/docs/document/content/reference/shadow/_index.en.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.6. </b>"
+pre = "<b>7.6. </b>"
title = "Shadow"
weight = 6
+++
diff --git a/docs/document/content/reference/sharding/_index.cn.md b/docs/document/content/reference/sharding/_index.cn.md
index 32a1735e701..182617d04ab 100644
--- a/docs/document/content/reference/sharding/_index.cn.md
+++ b/docs/document/content/reference/sharding/_index.cn.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.2. </b>"
+pre = "<b>7.2. </b>"
title = "数据分片"
weight = 2
chapter = true
diff --git a/docs/document/content/reference/sharding/_index.en.md b/docs/document/content/reference/sharding/_index.en.md
index f57fc79ac08..49a2cba0c39 100644
--- a/docs/document/content/reference/sharding/_index.en.md
+++ b/docs/document/content/reference/sharding/_index.en.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.2. </b>"
+pre = "<b>7.2. </b>"
title = "Sharding"
weight = 2
chapter = true
diff --git a/docs/document/content/reference/test/_index.cn.md b/docs/document/content/reference/test/_index.cn.md
index 0645d77ee8e..6fbac8d1083 100644
--- a/docs/document/content/reference/test/_index.cn.md
+++ b/docs/document/content/reference/test/_index.cn.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.7. </b>"
+pre = "<b>7.7. </b>"
title = "测试"
weight = 7
chapter = true
diff --git a/docs/document/content/reference/test/_index.en.md b/docs/document/content/reference/test/_index.en.md
index 618a62e5c55..abfc20fffc3 100644
--- a/docs/document/content/reference/test/_index.en.md
+++ b/docs/document/content/reference/test/_index.en.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.7. </b>"
+pre = "<b>7.7. </b>"
title = "Test"
weight = 7
chapter = true
diff --git a/docs/document/content/reference/transaction/_index.cn.md b/docs/document/content/reference/transaction/_index.cn.md
index 8417f94f966..e737c215c07 100644
--- a/docs/document/content/reference/transaction/_index.cn.md
+++ b/docs/document/content/reference/transaction/_index.cn.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.3. </b>"
+pre = "<b>7.3. </b>"
title = "分布式事务"
weight = 3
chapter = true
diff --git a/docs/document/content/reference/transaction/_index.en.md b/docs/document/content/reference/transaction/_index.en.md
index 03e03ca77a4..5cebc9f2596 100644
--- a/docs/document/content/reference/transaction/_index.en.md
+++ b/docs/document/content/reference/transaction/_index.en.md
@@ -1,5 +1,5 @@
+++
-pre = "<b>8.3. </b>"
+pre = "<b>7.3. </b>"
title = "Transaction"
weight = 3
chapter = true