databases in the same log . . . . . . . . . . . . . . . . . . . . . . 215 To distinguish databases and users in the same log . . . . . . . . . . . . . . . . . 216 To split into different log files . . . . yaml or properties leading incorrect result when loading Oracle metadata？ . . . . . . 369 7.9 API Change Histories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 7.9.1 ShardingSphere‐JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Spring namespace configuration change history . . . . . . . . . . . . . . . . . . 412 Spring Boot Starter Configuration . . . . . . .

when integrating ShardingSphere with Spring Boot 2.x ? . . . . . . . . . . . . . . . . 356 7.9 API Change Histories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 7.9.1 ShardingSphere‐JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Spring namespace configuration change history . . . . . . . . . . . . . . . . . . 399 Spring Boot Starter Configuration . . . . . . . c-core ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. 2.1.2 Rules Configuration ShardingSphere‐JDBC

. . 50 Third‐party Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 4.5.5 Observability 7.26 26. [Other] Why is the database sharding result not correct when using Proxool?312 7.8 API Change Histories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 7.8.1 ShardingSphere‐JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Spring namespace configuration change history . . . . . . . . . . . . . . . . . . 352 Spring Boot Starter Configuration . . . . . . .

ShardingSphere document, v5.2.0 ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. 3. Edit application.yml. spring: shardingsphere: transactions after sharding; • Support RC isolation level; • Rollback transaction according to undo log; • Support recovery committing transaction automatically after the service is down. Unsupported Type Apache ShardingSphere does not provide database high availability capability. It senses the change of databases’primary‐secondary relationship through a third‐party provided high availability solu‐

ShardingSphere document, v5.2.1 ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. 3. Edit application.yml. spring: shardingsphere: Supported • Support cross‐database transactions after sharding; • Rollback transaction according to undo log; • Support recovery committing transaction automatically after the service is down. Unsupported Type Apache ShardingSphere does not provide database high availability capability. It senses the change of databases’primary‐secondary relationship through a third‐party provided high availability solu‐

${latest.release.version} 14 Apache ShardingSphere document Notice: Please change ${latest.release.version} to the actual version. 3. Create YAML configuration file # JDBC database statistical indicators are collected through probes for display by third‐party applications. Logging The log can be easily expanded through the agent to provide more information for analyzing the system running e-jdbc ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. Sample Standalone Mode ModeConfiguration modeConfig

. . 70 Third‐party Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 3.4.5 Observability c-core ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. 2.1.2 2. Rules Configuration ShardingSphere‐JDBC the SQL that runs rightly in single‐node databases may not be right in the sharding database. The change of table name after sharding, or misconducts caused by operations such as pagination, order by or

${latest.release.version} 14 Apache ShardingSphere document Notice: Please change ${latest.release.version} to the actual version. 3. Create YAML configuration file # JDBC database statistical indicators are collected through probes for display by third‐party applications. Logging The log can be easily expanded through the agent to provide more information for analyzing the system running c-core ${latest.release.version} Notice: Please change ${latest.release.version} to the actual version. 9.1. ShardingSphere-JDBC 93 Apache ShardingSphere

classpath 中添加 jta.properties 来定制化 Atomikos 配置项。 详情请参见 Atomikos 官方文档 。 数据恢复 在项目的 logs 目录中会生成 xa_tx.log, 这是 XA 崩溃恢复时所需的日志，请勿删除。 Narayana 事务 背景信息 Apache ShardingSphere 提供 XA 事务，集成了 Narayana 的实现。 前提条件 com/r/seataio/seata‐server • https://hub.docker.com/r/apache/seata‐server 创建 undo_log 表 在每一个 ShardingSphere 涉及的真实数据库实例中创建 undo_log 表。SQL 的内容以 https://github.c om/apache/incubator‐seata/tree/v2.0.0/script/client/at/db EXISTS `undo_log` ( `branch_id` BIGINT NOT NULL COMMENT 'branch transaction id', `xid` VARCHAR(128) NOT NULL COMMENT 'global transaction id', `context` VARCHAR(128) NOT NULL COMMENT 'undo_log context,such

classpath 中添加 jta.properties 来定制化 Atomikos 配置项。 详情请参见 Atomikos 官方文档 。 数据恢复 在项目的 logs 目录中会生成 xa_tx.log, 这是 XA 崩溃恢复时所需的日志，请勿删除。 Narayana 事务 背景信息 Apache ShardingSphere 提供 XA 事务，集成了 Narayana 的实现。 前提条件 Server 按照 seata‐work‐shop 中的步骤，下载并启动 Seata 服务器。 创建 undo_log 表 在每一个分片数据库实例中执创建 undo_log 表（以 MySQL 为例）。 CREATE TABLE IF NOT EXISTS `undo_log` ( `id` BIGINT(20) NOT NULL AUTO_INCREMENT COMMENT 'increment COMMENT 'undo_log context,such as serialization', `rollback_info` LONGBLOB NOT NULL COMMENT 'rollback info', `log_status` INT(11) NOT NULL COMMENT '0:normal status,1:defense status', `log_created` DATETIME