. 495 /metadata/${databaseName}/rules/sharding/tables/t_order/versions/0 . . . . . . 496 /metadata/databaseName/schemas/{schemaName}/tables/t_order/versions/0 . . 496 /nodes/compute_nodes . . . . on the underlying database, which can scale computing and storage horizontally. D is tr ib ut ed T ra ns ac ti on Transactional capability is key to ensuring database integrity and security and is endings, are t_order_0 to t_order_9, and their logical table names are t_order. Actual Table Physical tables that exist in the horizontally sharded databases. Those are, t_order_0 to t_order_9 in the

. 524 /metadata/${databaseName}/rules/sharding/tables/t_order/versions/0 . . . . . . 525 /metadata/databaseName/schemas/{schemaName}/tables/t_order/versions/0 . . 525 /nodes/compute_nodes . . . . on the underlying database, which can scale computing and storage horizontally. D is tr ib ut ed T ra ns ac ti on Transactional capability is key to ensuring database integrity and security and is endings, are t_order_0 to t_order_9, and their logical table names are t_order. Actual Table Physical tables that exist in the horizontally sharded databases. Those are, t_order_0 to t_order_9 in the

. . . . . . . . . . . . . . . . . . . 498 8.4.1 Encryption How to solve that data encryption can’t work with JPA? . . . . 498 8.5 DistSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . endings, are t_order_0 to t_order_9, and their logical table names are t_order. Actual Table Physical tables that exist in the horizontally sharded databases. Those are, t_order_0 to t_order_9 in the or cross‐library association will occur, affecting query efficiency. For example, if the t_order table and t_order_item table are both sharded according to order_id and are correlated using order_id

. . . . . . . . . . . . . . . . 307 7.7.16 16. [Encryption] How to solve that data encryption can’t work with JPA? . 308 7.7.17 17. [DistSQL] How to set custom JDBC connection properties or connection Solution S olutions/ Fea- tures • Distributed Database* Data Security Database Gateway Stress T esting Data Sharding Data Encrypt Multi‐model Databases Sup‐ ported Shadow D atabase Readwrit ‘file://component1’, ‘file://component2’ SHOW CREATE USER user REPAIR TABLE t_order OPTIMIZE TABLE t_order CHECKSUM TABLE t_order CHECK TABLE t_order SET RESOURCE GROUP group_name DROP RESOURCE GROUP group_name

. . . . . . . . . . . . . . . . . . . 459 8.4.1 Encryption How to solve that data encryption can’t work with JPA? . . . . 459 8.5 DistSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . endings, are t_order_0 to t_order_9, and their logical table names are t_order. Actual Table Physical tables that exist in the horizontally sharded databases. Those are, t_order_0 to t_order_9 in the or cross‐library association will occur, affecting query efficiency. For example, if the t_order table and t_order_item table are both sharded according to order_id and are correlated using order_id

. . . . . . . . . . . . . . . . . . 362 7.8.17 [Encryption] How to solve that data encryption can’t work with JPA? . . . 362 7.8.18 [DistSQL] How to set custom JDBC connection properties or connection Solution S olutions/ Fea- tures • Distributed Database* Data Security Database Gateway Stress T esting Data Sharding Data Encrypt Heterogeneous Databases Sup‐ ported Shadow D atabase Readwrit COMPONENT ‘file://component1’, ‘file://component2’ REPAIR TABLE t_order OPTIMIZE TABLE t_order CHECKSUM TABLE t_order CHECK TABLE t_order SET RESOURCE GROUP group_name DROP RESOURCE GROUP group_name

. . . . . . . . . . . . . . . . . . 350 7.8.17 [Encryption] How to solve that data encryption can’t work with JPA? . . . 350 7.8.18 [DistSQL] How to set custom JDBC connection properties or connection Solution S olutions/ Fea- tures • Distributed Database* Data Security Database Gateway Stress T esting Data Sharding Data Encrypt Heterogeneous Databases Sup‐ ported Shadow D atabase Readwrit COMPONENT ‘file://component1’, ‘file://component2’ REPAIR TABLE t_order OPTIMIZE TABLE t_order CHECKSUM TABLE t_order CHECK TABLE t_order SET RESOURCE GROUP group_name DROP RESOURCE GROUP group_name

. 459 /metadata/${databaseName}/rules/sharding/tables/t_order/versions/0 . . . . . . 460 /metadata/databaseName/schemas/{schemaName}/tables/t_order/versions/0 . . 460 /nodes/compute_nodes . . . . 中表的逻辑标识。例：订单数据根据主键尾数拆 分为 10 张表，分别是 t_order_0 到 t_order_9，他们的逻辑表名为 t_order。 8.1. 数据分片 21 Apache ShardingSphere document 真实表 在水平拆分的数据库中真实存在的物理表。即上个示例中的 t_order_0 到 t_order_9。 绑定表 指分片规则一致的一组分片表。使用绑定 卡尔积关联或跨库关联，从而影响查询效率。例如：t_order 表和 t_order_item 表，均按照 order_id 分片，并且使用 order_id 进行关联，则此两张表互为绑定表关系。绑定表之间的多表关联查询不会出 现笛卡尔积关联，关联查询效率将大大提升。举例说明，如果 SQL 为： SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i

. 485 /metadata/${databaseName}/rules/sharding/tables/t_order/versions/0 . . . . . . 486 /metadata/databaseName/schemas/{schemaName}/tables/t_order/versions/0 . . 486 /nodes/compute_nodes . . . . 中表的逻辑标识。例：订单数据根据主键尾数拆 分为 10 张表，分别是 t_order_0 到 t_order_9，他们的逻辑表名为 t_order。 8.1. 数据分片 21 Apache ShardingSphere document 真实表 在水平拆分的数据库中真实存在的物理表。即上个示例中的 t_order_0 到 t_order_9。 绑定表 指分片规则一致的一组分片表。使用绑定 卡尔积关联或跨库关联，从而影响查询效率。例如：t_order 表和 t_order_item 表，均按照 order_id 分片，并且使用 order_id 进行关联，则此两张表互为绑定表关系。绑定表之间的多表关联查询不会出 现笛卡尔积关联，关联查询效率将大大提升。举例说明，如果 SQL 为： SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i

438 ix /metadata/${databaseName}/rules/sharding/tables/t_order/versions/0 . . . . . . 439 /metadata/databaseName/schemas/{schemaName}/tables/t_order/versions/0 . . 439 /nodes/compute_nodes . . . . 中表的逻辑标识。例：订单数据根据主键尾数拆 分为 10 张表，分别是 t_order_0 到 t_order_9，他们的逻辑表名为 t_order。 8.1. 数据分片 21 Apache ShardingSphere document 真实表 在水平拆分的数据库中真实存在的物理表。即上个示例中的 t_order_0 到 t_order_9。 绑定表 指分片规则一致的一组分片表。使用绑定 卡尔积关联或跨库关联，从而影响查询效率。例如：t_order 表和 t_order_item 表，均按照 order_id 分片，并且使用 order_id 进行关联，则此两张表互为绑定表关系。绑定表之间的多表关联查询不会出 现笛卡尔积关联，关联查询效率将大大提升。举例说明，如果 SQL 为： SELECT i.* FROM t_order o JOIN t_order_item i ON o.order_id=i