Weekly Report of ShardingSphere (2019.5.6-2019.5.10)

[Harper0122]

This report is to review recent changes and developments of ShardingSphere.

Basic Data

Basic data shows how the watch, star and fork have changed during the past week.

Watch	Star	Fork
868	7707	2650

This Week's Development

This part is to show new developments of ShardingSphere during the past week.

Feature Development

Architecture Design

1. Planned ShardingSphere's full-view v0.1.

New Module Development

1. Prepared for ShardingSphere‘s integration with Seata AT transactions (Support distributed transaction by integrating seata. #2335, doing).

Feature Optimization & Refactoring

1. Replaced the parser from its second generation to the third (Use 3rd generation parse engine instead of 2nd generation parse engine #2084, doing).
2. Added test examples for data masking (MySQL encrypt test #2191, done).
3. Reviewed how to optimize the rewrite engine; refactored placeholder (Reconstruct rewriting module #2275, doing).
4. Reviewed SQL parsing test examples (merge sharding sql parsing test case #2384, doing).
5. Split the token for the column name of INSERT INTO... SQL (Reconstruct Parsing, rewriting of INSERT statement. #2386, doing).
6. Added DataSourceGroupBroadcastRoutingEngine to deal with SHOW XXX DAL statements (While using database,it will select a random database!!! #2331, done).
7. The support for WHERE BETWEEN AND in data masking situations (Wrong result set for select between and when using encrypt data source #2398, done).

Problem Fix

1. The exception appeared when Sharding-JDBC inserts text data (got java.io.NotSerializableException when insert record to table which has text column #1567, java.io.NotSerializableException occurred when setting parameters into PreparedStatement #2105, java.io.NotSerializableException: java.io.StringReader #2181, done).
2. The exception appeared when Sharding-Proxy inserts blob data (blob column insert exception: Unknown exception: INSERT INTO column size mismatch value size #1910, done).
3. The rewrite error when a keyword is used as the column name in INSERT... (Insert error when field name was a keyword #2319, done).
4. Parsing failure when user is used as the table name (delete from user where id=“xx” parse error in shading-jdbc 4.0.0-RC1 #2379, done).

ShardingSphere Ecology Construction

Publicity

1. Apache ShardingSphere's Development at iFLY's WOT 2019.

Cooperation

1. Merged SkyWalking plug-in for ShardingSphere 3.0.0 (Provide plugin for ShardingSphere skywalking#1934, done).
2. Developed SkyWalking plug-in for ShardingSphere 4.0.0 (Provide plugin for ShardingSphere 4.0.0-RC1 skywalking#2699, doing).

Official Website

1. Optimized Read-Write Split, Other Features and Orchestration documents (incubator-shardingsphere-doc ShardingValue，TableRule 少了很多方法，为啥，1.4.0的版本 #175, AbstractMemoryResultSet对SQL的wasNull实现有问题 #176 and 只配置读写分离，获取的datasource不能区分master和slave #178).
2. Optimized document index (incubator-shardingsphere-doc#177, done).

Next Week's Plan

This part is to show ShardingSphere's plan for the next week.

Feature Development

New Module Development

1. Replace the parser from its second generation to the third (Use 3rd generation parse engine instead of 2nd generation parse engine #2084).
2. Develop doneSeataATShardingTransactionManager (Support distributed transaction by integrating seata. #2335).

Feature Optimization & Refactoring

1. Optimize INSERT SET parsing and rewrite.
2. Optimize SQLBuilder refactoring and splitting.

Problem Investigation

1. Issue Incorrect integer value: 'null' for column 'xxx' at row 1 #2336, mysql client can't get the proxy configuration dynamically. #2346 and too slow when application running,version:4.0.0-RC1 #2394.
2. The exception of physical-strategy indicator uses Hibernate (Error when use "spring.jpa.hibernate.naming.physical-strategy" #2393).

ShardingSphere Ecology Construction

Publicity

1. A WeChat article about chain tracing.

Cooperation

1. Develope SkyWalking plug-in for ShardingSphere 4.0.0 (Provide plugin for ShardingSphere 4.0.0-RC1 skywalking#2699).

Available Tasks for Community Committers

Issue #1775, #1907 and #1998.