ShardingSphere just like building lego blocks. There are lots of SPI extensions for Apache ShardingSphere now and increase continuously. ShardingSphere became an Apache Top Level Project on April 16, 2020. binary protocol to support heterogeneous languages. Friendlier to DBA, the MySQL version provided now can use any kind of terminal (such as MySQL Command Client, MySQL Workbench, etc.) that is compatible sharding key + sharding algorithm, i.e., the sharding strategy, can be used in sharding operation. For now, 4 kinds of sharding strategies are available. • Standard Sharding Strategy StandardShardingStrategy

database. 3.3.4 Notice DistSQL can use for ShardingSphere‐Proxy only, not for ShardingSphere‐JDBC now. 3.4 Pluggable Architecture 3.4.1 Background In Apache ShardingSphere, many functionality implementations ingSphere just like building lego blocks. There are lots of SPI extensions for Apache ShardingSphere now and increase continuously. 3.4.3 Goal It is the design goal of Apache shardingsphere pluggable architecture execution. The reason for that is the former SQL only needs to transmit 10 records to the user end, but now it will transmit 1,000,010 * 2 records after the rewrite. Optimization of ShardingSphere ShardingSphere

database. 3.3.4 Notice DistSQL can use for ShardingSphere‐Proxy only, not for ShardingSphere‐JDBC now. Source Codes: https://github.com/apache/shardingsphere/tree/master/shardingsphere‐distsql 3.4 Pluggable ingSphere just like building lego blocks. There are lots of SPI extensions for Apache ShardingSphere now and increase continuously. 3.4.3 Goal It is the design goal of Apache shardingsphere pluggable architecture execution. The reason for that is the former SQL only needs to transmit 10 records to the user end, but now it will transmit 1,000,010 * 2 records after the rewrite. Optimization of ShardingSphere ShardingSphere

database. 3.3.4 Notice DistSQL can use for ShardingSphere‐Proxy only, not for ShardingSphere‐JDBC now. 3.4 Pluggable Architecture 3.4.1 Background In Apache ShardingSphere, many functionality implementations ingSphere just like building lego blocks. There are lots of SPI extensions for Apache ShardingSphere now and increase continuously. 3.4.3 Goal It is the design goal of Apache shardingsphere pluggable architecture execution. The reason for that is the former SQL only needs to transmit 10 records to the user end, but now it will transmit 1,000,010 * 2 records after the rewrite. Optimization of ShardingSphere ShardingSphere

function, users need to set sqlCommentParseEnabled to true. The comment for‐ mat only supports /* */ for now. The content needs to start with SHARDINGSPHERE_HINT:, and an d optional attributes include: • {table} function, users need to set sqlCommentParseEnabled to true. The comment for‐ mat only supports /* */ for now. The content needs to start with SHARDINGSPHERE_HINT:, and the attribute name needs to be WRITE_ROUTE_ONLY ShardingSphere document, v5.2.1 ## @param compute.serverConfig.mode.type Type of mode configuration. Now only support Cluster mode ## @param compute.serverConfig.mode.repository.props.namespace Namespace

function, users need to set sqlCommentParseEnabled to true. The comment for‐ mat only supports /* */ for now. The content needs to start with ShardingSphere hint:, and the attribute name needs to be writeRouteOnly ShardingSphere document, v5.2.0 ## @param compute.serverConfig.mode.type Type of mode configuration. Now only support Cluster mode ## @param compute.serverConfig.mode.repository.props.namespace Namespace ephemeral data live ## @param compute.serverConfig.mode.repository.type Type of persist repository. Now only support ZooKeeper ## @param compute.serverConfig.mode.overwrite Whether overwrite persistent

Apache ShardingSphere document ## @param compute.serverConfig.mode.type Type of mode configuration. Now only support Cluster mode ## @param compute.serverConfig.mode.repository.props.namespace Namespace ephemeral data live ## @param compute.serverConfig.mode.repository.type Type of persist repository. Now only support ZooKeeper ## @param compute.serverConfig.mode.overwrite Whether overwrite persistent editing YAML. After With the advent of DistSQL, the operation of ShardingSphere has also changed: Now, the user experience has been greatly improved: ‐ Uses the same client to operate data and Shard‐

Apache ShardingSphere document ## @param compute.serverConfig.mode.type Type of mode configuration. Now only support Cluster mode ## @param compute.serverConfig.mode.repository.props.namespace Namespace ephemeral data live ## @param compute.serverConfig.mode.repository.type Type of persist repository. Now only support ZooKeeper ## @param compute.serverConfig.mode.overwrite Whether overwrite persistent of ShardingSphere has also changed: 9.2. ShardingSphere-Proxy 185 Apache ShardingSphere document Now, the user experience has been greatly improved: ‐ Uses the same client to operate data and Shard‐

important events in the scheduling process through event subscription for query, statistics and monitor. Now, the event subscription based on relation database is provided to record events, and developers can application and paste them into application. 6.3. Operation 76 Apache ShardingSphere ElasticJob document Now we can use it Function list • Login security control • Registration center, event tracking data

mode Configuration parameters ## @param compute.serverConfig.mode.type Type of mode configuration. Now only support Cluster mode ## @param compute.serverConfig.mode.repository.props.namespace Namespace ephemeral data live ## @param compute.serverConfig.mode.repository.type Type of persist repository. Now only support ZooKeeper ## @param compute.serverConfig.mode.overwrite Whether overwrite persistent 18086 Source data source lacks %s privilege(s). H Y000 18087 Source data source required ‘%s = %s‘, now is ‘%s‘. H Y000 18088 User ‘%s‘ does exist. 0 8000 18089 Check privileges failed on source data source