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
865	7647	2657

This Week's Development

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

Feature Development

Feature Optimization & Refactoring

1. Replaced the parsing engine from its second generation to the third (Use 3rd generation parse engine instead of 2nd generation parse engine #2084 doing).
2. The support of sharding-jdbc-spring-boot-start for JNDI data source configuration (How to config JNDI in datasource #2260, done).
3. Added RoutingHook in BaseShardingEngine (Add routing hook in BaseShardingEngine #2273, done).
4. Optimized SQLToken and refactored the rewrite engine (Reconstruct rewriting module #2275, done).
5. Optimized MySQL&Oracle&Postgres&SQLServer DDL Antlr parsing document structure (Review the DDL Parsing rules for different databases #2276, done).
6. COM_STMT_RESET and proxy were available to use preare statement through python client (sharding-proxy does not support COM_STMT_RESET command of mySQL #2303, done).
7. Sharding for MySQL REPLACE statement (Support REPLACE statement for MySQL #2315, done).
8. Reviewed the problem that insert with auto-increment key cannot be reverted (#shardingsphere-spi-impl jar包没有上传到maven中心库？ #44, done).
9. Reviewed the problem that Saga cannot be recovered once it is down (#shardingsphere-spi-impl 结点磁盘扩容，分片数据能自动迁移吗？还是必须手动导出？ #45, done).

Problem Fix

1. "Unable to serialize" exception after inserting any text field (got java.io.NotSerializableException when insert record to table which has text column #1567, doing).
2. Wrong null value in Sharding-Proxy (MySQL) query result (wrong result for the null value in int column  #2224, done).
3. Metadata was not refreshed after executing ALTER TABLE (select * missing column #2226, done).
4. Null value alert after the use of preparedStatemt and Insert Values( ) (insert with generated keys,when the last column value is null，cause NullPointerException #2252, done).
5. INSERT ... ON DUPLICATE KEY UPDATE execution error (INSERT ... ON DUPLICATE KEY UPDATE ,Reporting the following error #2271, done).
6. Not enough parsing information in UpdateStatement (missing revert information while filling UpdateStatement #2278, done).
7. Self-defined load balance strategy could not take effect in sharding+master-slave (The strategy of master-slave-rule is not valid #2306, done).
8. Rewrite error caused by index name with \ (If there is quoteCharacter for index name, sql can not be executed #2312, done).
9. MYSQL function name parsing error (SUM(IF(INTERVAL print error log "no viable alternative at input" #2324, done).
10. Error report of using Insert Set under Sharding (The SQL of insert set can not run well when sharding #2329, done).
11. Sharding-Proxy (PostgreSQL) did not support Chinese (Sharding-proxy Query result :extraneous data in "D" message ,reason: have chinese #2343, done).
12. Transactions could not take effect after python client connecting proxy (proxy transaction cannot work with python client. #2356, done).

ShardingSphere Ecology Construction

Official Website

1. Optimized Sharding-Proxy documents (incubator-shardingsphere-doc 获取自增序列SQL实现 #164).
2. Updated Rewritten Engine, Execution Engine and Merger Engine English documents (incubator-shardingsphere-doc 读写分离 不进行分库分表 #168, incubator-shardingsphere-doc sharding-jdbc-core配合自动生成序列改造 #171 and incubator-shardingsphere-doc 为什么我的issue被关了呢？ #173).
3. Added sharding-jdbc-spring-boot-start JNDI data source configuration documents (incubator-shardingsphere-doc 增加底层错误测试 #174).

Cooperation

1. Reached an agreement with Seata; prepared for the integration (Support distributed transaction by integrating seata. #2335, doing).
2. StreamBasedSaga Community discussion (#shardingsphere-spi-impl yaml文件中包含中文，且操作系统模式不是utf-8编码导致的yaml不能解析 #43, done).
3. Optimized SkyWalking plug-in test example (Provide plugin for ShardingSphere skywalking#1934, done).

Publicity

1. Apache ShardingSphere's Development at DTCC2019.

Community

1. Thanks for codes contributed by @weiyuc (PR fix bug #2312 #2320).

Next Week's Plan

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

Feature Development

New Module Development

1. Replace the parsing engine from its second generation to the third (Use 3rd generation parse engine instead of 2nd generation parse engine #2084).
2. Investigate ShardingSphere's integration of seata (Support distributed transaction by integrating seata. #2335).

Problem Investigation

1. "Unable to serialize" exception after inserting any text field (got java.io.NotSerializableException when insert record to table which has text column #1567).
2. Wrong show tables returned (While using database,it will select a random database!!! #2331).

Available Tasks for Community Committers

Issue #1775, #1907 and #2154.