Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weekly Report of ShardingSphere (2019.4.1 to 2019.4.4) #2163

Closed
Harper0122 opened this issue Apr 4, 2019 · 0 comments
Closed

Weekly Report of ShardingSphere (2019.4.1 to 2019.4.4) #2163

Harper0122 opened this issue Apr 4, 2019 · 0 comments

Comments

@Harper0122
Copy link
Contributor

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
860 7216 2546

This Week's Development

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

Feature Development

New Feature Development

  1. The access support for independent data source masking of SpringBoot&SpringNameSpace ( - Lose result set when use DISTINCT syntax. #2094 finished).
  2. sharding-orchestration-reg-jetcd module ( - 去除多余的判断 #34 finished).
  3. Example

Bug Fix

  1. Fixed the problem when using DISTINCT + GROUP BY syntax at the same time, the query result set is wrong ( - Lose result set when use DISTINCT syntax. #2094 finished).
  2. Fixed LIMIT multi-thread problem ( - (mybatis + shardingjdbc ) multithreading paging query Incorrect result  #2136 finished).

Feature Optimization & Refactoring

  1. Improved the performance of data masking query ( - Sharding Encryptor #1844 finished).
  2. Improved SHOW TABLES performance ( - SQL Show tables are show when config huge mount of actual tables #2153 finished).
  3. Replaced the parsing engine from its second generation to the third in phase ( - Use 3rd generation parse engine instead of 2nd generation parse engine #2084 doing).
  4. Developed examples of sharding data masking test ( - MySQL sharding encrypt test #2134 doing).

ShardingSphere Ecology Construction

Official Website Construction

  1. Supplemented the instances of independent data source masking in official documents.

Release

  1. Split bin release to sharding-jdbc-bin and sharding-proxy-bin ( - Release distribution  #2147 finished).
  2. Finished the second round of test of 4.0.0-RC1-release.

Publicity

  1. Wrote The Practical Implementation of Distributed Database Middleware Apache ShardingSphere at JD and and published it on the official WeChat account of DBAPlus and JD Finance Cloud.

Next Week's Plan

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

Feature Development

New Feature Development

  1. Example
  2. Add registry center spi in the registry center of orchestration module; distinguish between zookeeper/etcd and other possible registry centers such as eureka.

Problem Investigation

  1. The exception thrown by getColumnIndex when columnLabel in Oracle JDBC ResultSetMetaData is fixed to be capitalized ( - MemoryQueryResult getColumnIndex throw exception when using Oracle database #2152).
  2. The problem of error type shift when Oracle JDBC searches time field ( - ShardingResultSet getTimestamp throw ClassCastException when using oracle database #2159).

Feature Optimization & Refactoring

  1. Replace the parsing engine from its second generation to the third in phase ( - Use 3rd generation parse engine instead of 2nd generation parse engine #2084).
  2. Develop examples of sharding data masking test.

ShardingSphere Ecology Construction

Release

  1. Finish the third round of test.
  2. Call for the vote in ShardingSphere community.

Available Tasks for Community Committers

Issue #1775, #1907, #2110, #2148, #2154 and #2158.

@Harper0122 Harper0122 changed the title Weekly Report of ShardingSphere (2019-3-8 to 2019-3-15) Weekly Report of ShardingSphere (2019.4.1 to 2019.4.4) Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants