267 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Procedure . . means one or multiple can be included [] means array, can substitutable with - each other Mode Parameters mode (?): # Default value is Standalone type: # Type of mode configuration. Values could be: Alibaba Druid 1.2.9, using url instead of jdbcUrl in the example below is the expected behavior. Parameters dataSources: # Data sources configuration, multiple available :

vi Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Procedure . . means one or multiple can be included [] means array, can substitutable with - each other Mode Parameters mode (?): # Default value is Standalone type: # Type of mode configuration. Values could be: Alibaba Druid 1.2.9, using url instead of jdbcUrl in the example below is the expected behavior. Parameters dataSources: # Data sources configuration, multiple available :

429 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430 Procedure . . 457 Use specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 SQL Hint . . means one or multiple can be included [] means array, can substitutable with - each other Mode Parameters mode (?): # Default value is Standalone type: # Type of mode configuration. Values could be:

398 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Procedure . . 426 Use specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 SQL Hint . . means one or multiple can be included [] means array, can substitutable with - each other Mode Parameters mode (?): # Default value is Standalone type: # Type of mode configuration. Values could be:

property script.command.line, without coding. The script path can contain parame‐ ters, after the parameters are passed, the job framework will automatically append the last parameter as the job runtime divided into two types: timed scheduling and one‐time scheduling. Each sched‐ uler needs three parameters: registry configuration, job object (or job type), and job configuration when it starts. Timed job configuration Method signature：YamlJobConfiguration getJobConfiguration(String jobName) • Parameters: – jobName —Job name • Returns: Job configuration object Update job configuration Method signature：void

getJobConfiguration(String jobName) • Parameters: – jobName —作业名称 • Returns: 作业配置对象 更新作业配置 方法签名：void updateJobConfiguration(YamlJobConfiguration yamlJobConfiguration) • Parameters: – jobConfiguration —作业配置对象 —作业配置对象 删除作业设置 方法签名：void removeJobConfiguration(String jobName) • Parameters: – jobName —作业名称 6.1. 使用手册 50 Apache ShardingSphere ElasticJob document 操作类 API 类名称：org.apache.shardingsphere.elasticjob Optional serverIp) • Parameters: – jobName —作业名称 – serverIp —作业服务器 IP 地址 禁用作业 禁用作业将会导致分布式的其他作业触发重新分片。 方法签名：void disable(Optional jobName, Optional serverIp) • Parameters: – jobName —作业名称 – serverIp

type (+) String Database discov‐ ery type, such as: MySQL.MGR • props (?) Pr operties Required parameters for high‐availability types, such as MGR’s group‐name • Encryption Root Configuration Class type, such as: MySQL.MGR props (?): group-name: 92504d5b-6dec-11e8-91ea-246e9612aaf1 # Required parameters for database discovery types, such as MGR's group-name Distributed Transaction Configuration shardingsphere.rules.database-discovery.discovery-types..props.group-name= # Required parameters for database discovery types, such as MGR's group-name Encryption Configuration Item Explanation

(+) String Database discovery type, such as: MGR、 openGauss • props (?) Pr operties Required parameters for high‐availability types, such as MGR’s group‐name • Encryption Root Configuration Class such as: MGR、openGauss props (?): group-name: 92504d5b-6dec-11e8-91ea-246e9612aaf1 # Required parameters for database discovery types, such as MGR's group-name Encryption Configuration Item Explanation shardingsphere.rules.database-discovery.discovery-types..props.group-name= # Required parameters for database discovery types, such as MGR's group-name Encryption Configuration Item Explanation

Usage Use OpenTracing • Method 1: inject Tracer provided by APM system through reading system parameters Add startup arguments -Dorg.apache.shardingsphere.tracing.opentracing.tracer.class=org.apache SQL-TYPE/ SQL-TYPE-integration-test-cases.xml. This file just like an index, defined the sql, parameters and expected index position for execution. the SQL is the value for sql-case-id. For example: sql-case-id="insert_with_all_placeholders"> parameters="1:int, 1:int, insert:String" expected-data-file= "insert_for_order_1.xml" /> parameters="2:int, 2:int, insert:String" expected-data-file=

Usage Use OpenTracing • Method 1: inject Tracer provided by APM system through reading system parameters Add startup arguments -Dorg.apache.shardingsphere.tracing.opentracing.tracer.class=org.apache and props. Type is defined by the algorithm in SPI, and props is used to deliver the customized parameters of the algorithm. No matter which configuration type is used, the configured algorithm is named Description name Sharding algorithm name type Sharding algorithm type props Sharding algorithm parameters Sharding Binding Table Rule Column Description sharding_binding_tables sharding Binding Table