Apache ShardingSphere 5.0.0-alpha Documentprovided by different database dialect, it is categorized into keyword, expression, literal value and operator. SQL is then converted into abstract syntax tree by syntactic parser. For example, the following single‐sharding route (equal mark as the operator of sharding key), multiple‐sharding route (IN as the operator of sharding key) and range sharding route (BETWEEN as the operator of sharding key). SQL without sharding not include joint query or only includes joint query between binding tables. When the sharding operator is equal mark, the route result will fall into a single database (table); when sharding operators0 码力 | 311 页 | 2.09 MB | 1 年前3
Apache ShardingSphere 5.4.1 Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 8.1.8 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 8.2 Distributed Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 8.2.9 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 8.3 Readwrite‐splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 8.7.8 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 8.8 Data Masking . . . . . . . . .0 码力 | 572 页 | 3.73 MB | 1 年前3
Apache ShardingSphere v5.5.0 document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 8.1.8 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 8.2 Distributed Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 8.2.9 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 8.3 Readwrite‐splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 8.7.8 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 8.8 Data Masking . . . . . . . . .0 码力 | 602 页 | 3.85 MB | 1 年前3
Apache ShardingSphere ElasticJob document Nov 01, 2023module is still in incubation. Configuration API Class name: org.apache.shardingsphere.elasticjob.lifecycle.api. JobConfigurationAPI Get job configuration Method signature:YamlJobConfiguration getJobConfiguration(String Parameters: – jobName —Job name Operation API Class name:org.apache.shardingsphere.elasticjob.lifecycle.api.JobOperateAPI 6.1. Usage 50 Apache ShardingSphere ElasticJob document Trigger job execution address of the job server Operate sharding API Class name:org.apache.shardingsphere.elasticjob.lifecycle.api. ShardingOperateAPI Disable job sharding Method signature:void disable(String jobName, String0 码力 | 101 页 | 1.53 MB | 1 年前3
Apache ShardingSphere 5.2.1 Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.1.8 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.2 Distributed Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.2.9 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 ii 3.3 Readwrite‐splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.8.8 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.9 Shadow . . . . . . . . . . . .0 码力 | 523 页 | 4.51 MB | 1 年前3
Apache ShardingSphere 5.2.0 Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.1.8 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3.2 Distributed Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 ii 3.2.9 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 3.3 Readwrite‐splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 3.8.8 Appendix with SQL operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 3.9 Shadow . . . . . . . . . . . .0 码力 | 483 页 | 4.27 MB | 1 年前3
Apache ShardingSphere ElasticJob 中文文档 2023 年 11 月 01 日API,可以通过直接对注册中心进行操作的方式控制作业在分布式环境下的生命周 期。 该模块目前仍处于孵化状态。 配置类 API 类 名 称:org.apache.shardingsphere.elasticjob.lifecycle.api. JobConfigurationAPI 获取作业配置 方法签名:YamlJobConfiguration getJobConfiguration(String jobName) 50 Apache ShardingSphere ElasticJob document 操作类 API 类名称:org.apache.shardingsphere.elasticjob.lifecycle.api.JobOperateAPI 触发作业执行 作业在不与当前运行中作业冲突的情况下才会触发执行,并在启动后自动清理此标记。 方法签名:void trigger(Optional jobName – jobName —作业名称 – serverIp —作业服务器 IP 地址 操作分片的 API 类名称:org.apache.shardingsphere.elasticjob.lifecycle.api.ShardingOperateAPI 禁用作业分片 方法签名:void disable(String jobName, String item) • Parameters: –0 码力 | 98 页 | 1.97 MB | 1 年前3
Apache ShardingSphere 5.0.0 Documenteach data node to manage their own transactions on the premise that any distributed trans‐ action manager is not on. They do not have any coordination and communication ability, or know other data nodes Model defined by X/OPEN, in which created AP (Application Pro‐ gram), TM (Transaction Manager) and RM (Resource Manager) can guarantee a high transaction con‐ sistency. TM and RM use XA protocol for bidirectional XA driver provided by database manufacturers and TransactionManager is provided by trans‐ action manager manufacturers. Traditional transaction managers need to be bound with application server, which0 码力 | 403 页 | 3.15 MB | 1 年前3
Apache ShardingSphere 5.1.1 Documenteach data node to manage their own transactions on the premise that any distributed trans‐ action manager is not on. They do not have any coordination and communication ability, or know other data nodes Model defined by X/OPEN, in which created AP (Application Pro‐ gram), TM (Transaction Manager) and RM (Resource Manager) can guarantee a high transaction con‐ sistency. TM and RM use XA protocol for bidirectional XA driver provided by database manufacturers and TransactionManager is provided by trans‐ action manager manufacturers. Traditional transaction managers need to be bound with application server, which0 码力 | 458 页 | 3.43 MB | 1 年前3
Apache ShardingSphere 5.1.2 Documenteach data node to manage their own transactions on the premise that any distributed trans‐ action manager is not on. They do not have any coordination and communication ability, or know other data nodes Model defined by X/OPEN, in which created AP (Application Pro‐ gram), TM (Transaction Manager) and RM (Resource Manager) can guarantee a high transaction con‐ sistency. TM and RM use XA protocol for bidirectional XA driver provided by database manufacturers and TransactionManager is provided by trans‐ action manager manufacturers. Traditional transaction managers need to be bound with application server, which0 码力 | 503 页 | 3.66 MB | 1 年前3
共 22 条
- 1
- 2
- 3













