. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . .

Shadow Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 5.1.8 Special API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Sharding . connect to ShardingSphere‐Proxy, if ShardingSphere‐Proxy does not create a Schema or does not add a Resource, the client connection will fail? . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 7 adding a data source using DistSQL? . . . . . . . . . . . . . . . 362 7.8.19 [DistSQL] How to solve Resource [xxx] is still used by [Sin- gleTableRule]. exception when dropping a data source using DistSQL

Shadow Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 5.1.7 Special API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Sharding . connect to ShardingSphere‐Proxy, if ShardingSphere‐Proxy does not create a Schema or does not add a Resource, the client connection will fail? . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 7 adding a data source using DistSQL? . . . . . . . . . . . . . . . 350 7.8.19 [DistSQL] How to solve Resource [xxx] is still used by [Sin- gleTableRule]. exception when dropping a data source using DistSQL

DistSQL is divided into RDL, RQL and RAL. • RDL (Resource & Rule Definition Language) responsible for the definition of resources and rules; • RQL (Resource & Rule Query Language) responsible for the query query of resources and rules; • RAL (Resource & Rule Administration Language) responsible for the added‐on administrator fea‐ ture of hint, transaction type switch, sharding execute planning and so on TABLE t_order CHECK TABLE t_order SET RESOURCE GROUP group_name DROP RESOURCE GROUP group_name CREATE RESOURCE GROUP group_name TYPE = SYSTEM ALTER RESOURCE GROUP rg1 VCPU = 0‐63 4.1. DB Compatibility

thread. In addition to the programming method, Apache ShardingSphere also plans to cite Hint through special notation in SQL, so that users can use that function in a more transparent way. The SQL designated provided 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

mask_before_special_chars_mask telephone: maskAlgorithm: keep_first_n_last_m_mask maskAlgorithms: md5_mask: type: MD5 mask_before_special_chars_mask: type: MASK_BEFORE_SPECIAL_CHARS props: special-chars: MaskColumnRuleConfiguration emailColumn = new MaskColumnRuleConfiguration( "email", "mask_before_special_chars_mask"); MaskColumnRuleConfiguration telephoneColumn = new MaskColumnRuleConfiguration("telephone" ops.put("special-chars", "@"); beforeSpecialCharsProps.put("replace-char", "*"); maskAlgorithmConfigs.put("mask_before_special_chars_mask", new AlgorithmConfiguration("MASK_BEFORE_SPECIAL_CHARS", b

mask_before_special_chars_mask telephone: maskAlgorithm: keep_first_n_last_m_mask maskAlgorithms: md5_mask: type: MD5 mask_before_special_chars_mask: type: MASK_BEFORE_SPECIAL_CHARS props: special-chars: MaskColumnRuleConfiguration emailColumn = new MaskColumnRuleConfiguration( "email", "mask_before_special_chars_mask"); MaskColumnRuleConfiguration telephoneColumn = new MaskColumnRuleConfiguration("telephone" ops.put("special-chars", "@"); beforeSpecialCharsProps.put("replace-char", "*"); maskAlgorithmConfigs.put("mask_before_special_chars_mask", new AlgorithmConfiguration("MASK_BEFORE_SPECIAL_CHARS", b