[GitHub] [incubator-shardingsphere] Harper0122 opened a new issue #2049: Weekly Report of ShardingSphere (2019-3-8 to 2019-3-15)

[GitBox <gi...@apache.org>]

Harper0122 opened a new issue #2049: Weekly Report of ShardingSphere (2019-3-8 to 2019-3-15)
URL: https://github.com/apache/incubator-shardingsphere/issues/2049
 
 
   # Weekly Report of ShardingSphere (2019-3-8 to 2019-3-15)
   
   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
   -- | -- | --
   850 | 6985 | 2470
   
   ## This Week's Development
   
   This part is to show new developments of ShardingSphere during the past week.
   
   ### Feature Development
   
   #### New Module Development
   
   1. Finished the data desensitization communication work with Data Security Sector of JD Digital; joint test can start next week.
   2. Wrote test examples of independent & sharding desensitization data source.
   3. Added Docker-Compose start configuration of Sharding-JDBC and Sharding-Proxy.
   4. SPI of Sharding-Proxy transaction module.
   
   #### Feature Optimization & Refactoring
   
   1. Refactored Sharding-Core module; decoupled `api/common/parse/optimize/rewrite/route/execute/merge` module of it.
   2. Optimized the optimize and data desensitization modules of Sharding-Core.
   3. Transferred and refactored ShardingSphere-Examples project.
   
   #### Bug Fix
   
   1. Fixed the problem that Insert parsing result can not be stored and executed rightly in multiple-thread concurrence.
   2. Fixed the problem that Sharding-Proxy will not return error response in exception.
   3. Fixed the problem that SQL loses space parsing.
   4. Fixed space parsing problem in DB. TABLE.
   5. Fixed the problem that it will report errors when XA transaction resources repeat to inject in one thread with multiple ShardingConnections.
   6. Fixed the problem that INSERT statements will report error when Sharding-Proxy uses PrepareStatement.
   
   #### Issue
   
   1. Respond to #1979, #2012, #1971, #1967, #1954, #2036, #2034, #1711, #1827, #1980 and #1990.
   
   ### ShardingSphere Ecology Construction
   
   #### Official Website Construction
   
   1. Upgraded  official ShardingSphere-4.0.0 documents.
   2. Added English documents of Data Desensitization, Performance Test Report, Manual and Sharding-Proxy chapters.
   3. Added official documents of ShardingSphere distributed transaction Saga modules.
   
   #### Release Preparation
   
   1. Proofread and replaced ShardingSphere Apache Release Copyright.
   2. Changed and replaced ShardingSphere POM document version.
   
   ## Next Week's Plan
   
   This part is to show  ShardingSphere's plan for the next week.
   
   ### Feature Development
   
   #### New Module Development
   
   1. Joint decryption test of ShardingSphere data desensitization with Data Security Sector of JD Digital.
   2. Independent ShardingSphere  encrypted data source test in multiple scenarios.
   3. Add the support of SpringBoot start and Orchestration configuration to Collection parameter.
   4. Distributed transaction automation integrated test and coding.
   
   #### Problem Investigation
   
   1. Investigate the route and query problem of the master database under read-write split scenario.
   2. Investigate the problem that SHOW COLUMNS will report error under multiple Schema of Sharding-Proxy read-write split scenario.
   
   ### ShardingSphere Ecology Construction
   
   #### Official Website Construction
   
   1. Write official documents of distributed transactions.
   
   #### Publicity
   
   1. ShardingSphere Technology Presentation at DBAPlus Community (20:00, Wednesday, March 15, 2019)
   2. ShardingSphere Technology Presentation at JDDTechTalk (14:00, Saturday, March 23, 2019)
   
   #### Release Preparation
   
   1. Simulate ShardingSphere-4.0.0 Apache Release.

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