You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2019/05/13 05:49:03 UTC
[GitHub] [incubator-shardingsphere] Harper0122 opened a new issue #2372:
Weekly Report of ShardingSphere (2019.5.6-2019.5.10)
Harper0122 opened a new issue #2372: Weekly Report of ShardingSphere (2019.5.6-2019.5.10)
URL: https://github.com/apache/incubator-shardingsphere/issues/2372
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 (#2084 doing).
2. The support of sharding-jdbc-spring-boot-start for JNDI data source configuration (#2260, done).
3. Added RoutingHook in BaseShardingEngine (#2273, done).
4. Optimized SQLToken and refactored the rewrite engine (#2275, done).
5. Optimized MySQL&Oracle&Postgres&SQLServer DDL Antlr parsing document structure (#2276, done).
6. COM_STMT_RESET and proxy were available to use preare statement through python client (#2303, done).
7. Sharding for MySQL REPLACE statement (#2315, done).
8. Reviewed the problem that `insert` with auto-increment key cannot be reverted (#shardingsphere-spi-impl #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 (#1567, doing).
2. Wrong null value in Sharding-Proxy (MySQL) query result (#2224, done).
3. Metadata was not refreshed after executing ALTER TABLE (#2226, done).
4. Null value alert after the use of preparedStatemt and Insert Values( ) (#2252, done).
5. `INSERT ... ON DUPLICATE KEY UPDATE` execution error (#2271, done).
6. Not enough parsing information in UpdateStatement (#2278, done).
7. Self-defined load balance strategy could not take effect in sharding+master-slave (#2306, done).
8. Rewrite error caused by index name with \ (#2312, done).
9. MYSQL function name parsing error (#2324, done).
10. Error report of using Insert Set under Sharding (#2329, done).
11. Sharding-Proxy (PostgreSQL) did not support Chinese (#2343, done).
12. Transactions could not take effect after python client connecting proxy (#2356, done).
### ShardingSphere Ecology Construction
#### Official Website
1. Optimized Sharding-Proxy documents (incubator-shardingsphere-doc #164).
2. Updated Rewritten Engine, Execution Engine and Merger Engine English documents (incubator-shardingsphere-doc #168, incubator-shardingsphere-doc #171 and incubator-shardingsphere-doc #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 (#2335, doing).
2. StreamBasedSaga Community discussion (#shardingsphere-spi-impl #43, done).
3. Optimized SkyWalking plug-in test example (https://github.com/apache/skywalking/pull/1934, done).
#### Publicity
1. *Apache ShardingSphere's Development* at DTCC2019.
#### Community
1. Thanks for codes contributed by @weiyuc (PR #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 (#2084).
2. Investigate ShardingSphere's integration of seata (#2335).
#### Problem Investigation
1. "Unable to serialize" exception after inserting any text field (#1567).
2. Wrong show tables returned (#2331).
## Available Tasks for Community Committers
Issue #1775, #1907 and #2154.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services