4.0.0

API Changes

1. Change package and maven groupId form io.shardingsphere to org.apache.shardingsphere.
2. Adjust Sharding-JDBC configuration API.
3. Adjust persist structure for registry center.

New Features

1. SQL92 Syntax available.
2. Sharding-Proxy for PostgreSQL protocol available.
3. SQL 100% compatible if route to single data node.
4. Less-than(<), greater-than(>) and Less-than-equal(<=), greater-than-equal(>=) for sharding key operator available.
5. DISTINCT SQL syntax available.
6. Broadcast table available.
7. LEAF key generator available.
8. XA Transaction available, Atomikos, Narayana and Bitronix integrated.
9. BASE Transaction available, Seata integrated.
10. Data encrypt available.
11. Skywalking plugin available.
12. Sharding-UI available, an orchestration management platform.

Enhancement

1. MariaDB supported.
2. Improve the compatibility of SQL parsing.
3. SELECT FOR UPDATE route to master data source only.
4. Hint in Sharding-Proxy available.
5. Make configuration of orchestration consistent between Sharding-JDBC and Sharding-Proxy.
6. Renew modified data sources only, not renew all the data sources.
7. Vibrate configurable for Snowflake key generator.

Bug Fixes

1. Improve the compatibility of JDBC Driver URL.
2. Delete statement with alias available.
3. Check and disable updating sharding column.
4. Fix wrong type of TINYINT and SMALLINT as INTEGER.

Change Logs

1. MILESTONE #3
2. MILESTONE #4
3. MILESTONE #5
4. MILESTONE #6
5. MILESTONE #7
6. MILESTONE #8
7. MILESTONE #9

4.0.0-RC3

New Features

1. Sharding-UI, an orchestration management platform for ShardingSphere comes online.
2. Not only SQLs from MySQL, PostgreSQL, SQLServer, Oracle, but any SQL92 Syntax can be parsed correctly and used in ShardingSphere.

Enhancement

1. Support using less-than character(<) and greater-than character(>) for sharding data.
2. When master and slave dataSources exist, support executing SELECT FOR UPDATE on master dataSource.
3. Support hint in Sharding-Proxy.
4. Finish parsing DAL syntax for MySQL.
5. Make configuration of orchestration compatible between Sharding-JDBC and Sharding-Proxy.

Bug Fixes

1. Through Bug fix, the feature of encryption becomes much stable and applicable.
2. Support delete statement with alias.
3. Check and disable updating sharding column.
4. Fix wrong type of TINYINT and SMALLINT as INTEGER.

Refactor

1. Rename optimized module to preprocessor module.
2. Decouple rewrite core module for sharding/encrypt features.

Change Logs

1. MILESTONE

4.0.0.RC2

API Changes

1. Optimize and delete API and configuration item of sharding logic index.
2. Update the API of encryption to support the encrypted and plain data coexistence.

New Features

1. Integration of Seata for distributed transaction.
2. User can do data encryption by using ShardingProxy.
3. User can use Leaf-segment generator to get distributed ID.
4. Support Skywalking plugin for application performance management.

Enhancement

1. Renew modified dataSources, not all the datasources to improve performance for configuration orchestration.
2. Improve the compatibility of SQL parsing.

Refactor

1. Remove DatabaseType enum, use dynamic SPI to load data source type.
2. The parse engine upgrade from the 2nd generation to 3rd.
3. The Refactoring of SQL rewriting module.

Change Logs

1. MILESTONE

Merge all change logs of version 3.1.0.M1, 3.1.0, 3.1.0.1 and 4.0.0.M1. First apache release.

API Changes

1. Adjust persist structure for orchestration's registry center.
2. Adjust Sharding-JDBC configuration API.
3. Change package and maven groupId form io.shardingsphere to org.apache.shardingsphere.
4. Adjust spring-boot-starter.

New Features

1. XA Transaction available.
2. Data encrypt available.
3. Use PostgreSQL protocol access Sharding-Proxy available.
4. DISTINCT SQL syntax available.
5. Broadcast table.
6. All SQL 100% compatible if route to single data node (MySQL Only).

Change Logs

1. MILESTONE #3
2. MILESTONE #4
3. MILESTONE #5
4. MILESTONE #6

Milestones

1. Sharding-Proxy launch. Support the use of Sharding-Sphere in the form of database to support for MySQL CLI and GUI client

New Features

Core

1. ISSUE #290 Support batch INSERT
2. ISSUE #501 Support OR
3. ISSUE #980 Support DCL
4. ISSUE #1111 Support MySQL DAL

Sharding-Proxy

1. ISSUE #902 Support XA transaction
2. ISSUE #916 Support authorization
3. ISSUE #936 Support registry center
4. ISSUE #1046 Support multiple logic databases

Enhancements

Core

1. ISSUE #373 Support order by ?
2. ISSUE #610 Route unicast for DQL without table
3. ISSUE #701 Caching parsed results to improve performance
4. ISSUE #773 Support sharding and autoincrement key of INSERT without column names
5. ISSUE #935 Use YAML instead of JSON to store configurations in registry center
6. ISSUE #1004 Properties can configure for Sharding and Master-slave independent
7. ISSUE #1205 Execute engine enhancement

Sharding-JDBC

1. ISSUE #652 Support Spring Boot Starter 2.X
2. ISSUE #702 Support $->{..} for inline expression
3. ISSUE #719 Support inject key generator objects by spring namespace
4. ISSUE #720 Support inject sharding algorithm objects by spring namespace

Sharding-Opentracing

1. ISSUE #1172 Opentracing enhancement

API changes

1. ISSUE #1153 Adjust the maven artifactId for Orchestration module
2. ISSUE #1203 Adjust Spring namespace xsd for Sharding and Master-slave
3. ISSUE #1289 Adjust Hint API
4. ISSUE #1302 Refine package structure
5. ISSUE #1305 Deprecated and remove sharding-jdbc-transaction-parent module
6. ISSUE #1382 Remove type configuration in Orchestration module

Bug Fixes

Core

1. ISSUE #569 Failed to parse SQL for Oracle when ROWNUM is not at end
2. ISSUE #628 Support data type jsonb for PostgreSQL
3. ISSUE #646 When aliases in SELECT ITEMS correspond to the real column names of GROUP BY or ORDER BY, there is no need to generate derived columns
4. ISSUE #806 NOT IN parse exception
5. ISSUE #827 Endless loop for bad SQL like SELECT * FROM table WHERE id IN ()
6. ISSUE #919 Inline expression with groovy may cause memory leak
7. ISSUE #993 Fail to parsing PostgreSQL due to the quotation
8. ISSUE #1015 Support SQL like SELECT id, COUNT(*) FROM table GROUP BY 1,2
9. ISSUE #1120 Derived columns of GROUP BY / ORDER BY appear in query result
10. ISSUE #1186 Dead lock may occur on MEMORY_STRICTLY mode when get connection on concurrency environment
11. ISSUE #1265 RoundRobinMasterSlaveLoadBalanceAlgorithm throw an ArrayIndexOutOfBoundsException when AtomicInteger overflow

Sharding-JDBC

1. ISSUE #372 Reuse PreparedStatement cause cache of route result do not clean
2. ISSUE #629 Support transaction isolation on JDBC
3. ISSUE #735 Unexpected slave datasource routing result when using Round-robin load-balance algorithm in Mybatis
4. ISSUE #1011 Can't resolve placeholder in Spring Boot YAML configuration

API Changes

1. Adjust persist structure for orchestration's registry center.
2. Adjust Sharding-JDBC configuration API.

New Features

1. XA Transaction available.
2. All SQL 100% compatible if route to single data node (MySQL Only).
3. DISTINCT SQL syntax available.
4. Broadcast table available.
5. Solve data lean problem when using DefaultKeyGenerator with low TPS.

Change Logs

1. MILESTONE #3
2. MILESTONE #4

API changes

1. Adjust persist structure for orchestration's registry center.
2. Adjust Sharding-JDBC configuration API.

New Features

1. XA Transaction available.
2. All SQL 100% compatible if route to single data node (MySQL Only).
3. DISTINCT SQL syntax available.
4. Broadcast table available.
5. Solve data lean problem when using DefaultKeyGenerator with low TPS.

Change Logs for Issues and Pull requests

Milestones

1. Sharding-Proxy launch. Support the use of Sharding-Sphere in the form of database to support for MySQL CLI and GUI client

New Features

Core

1. ISSUE #290 Support batch INSERT
2. ISSUE #501 Support OR
3. ISSUE #980 Support DCL
4. ISSUE #1111 Support MySQL DAL

Sharding-Proxy

1. ISSUE #902 Support XA transaction
2. ISSUE #916 Support authorization
3. ISSUE #936 Support registry center
4. ISSUE #1046 Support multiple logic databases

Enhancements

Core

1. ISSUE #373 Support order by ?
2. ISSUE #610 Route unicast for DQL without table
3. ISSUE #701 Caching parsed results to improve performance
4. ISSUE #773 Support sharding and autoincrement key of INSERT without column names
5. ISSUE #935 Use YAML instead of JSON to store configurations in registry center
6. ISSUE #1004 Properties can configure for Sharding and Master-slave independent
7. ISSUE #1205 Execute engine enhancement

Sharding-JDBC

1. ISSUE #652 Support Spring Boot Starter 2.X
2. ISSUE #702 Support $->{..} for inline expression
3. ISSUE #719 Support inject key generator objects by spring namespace
4. ISSUE #720 Support inject sharding algorithm objects by spring namespace

Sharding-Opentracing

1. ISSUE #1172 Opentracing enhancement

API changes

1. ISSUE #1153 Adjust the maven artifactId for Orchestration module
2. ISSUE #1203 Adjust Spring namespace xsd for Sharding and Master-slave
3. ISSUE #1289 Adjust Hint API
4. ISSUE #1302 Refine package structure
5. ISSUE #1305 Deprecated and remove sharding-jdbc-transaction-parent module
6. ISSUE #1382 Remove type configuration in Orchestration module

Bug Fixes

Core

1. ISSUE #569 Failed to parse SQL for Oracle when ROWNUM is not at end
2. ISSUE #628 Support data type jsonb for PostgreSQL
3. ISSUE #646 When aliases in SELECT ITEMS correspond to the real column names of GROUP BY or ORDER BY, there is no need to generate derived columns
4. ISSUE #806 NOT IN parse exception
5. ISSUE #827 Endless loop for bad SQL like SELECT * FROM table WHERE id IN ()
6. ISSUE #919 Inline expression with groovy may cause memory leak
7. ISSUE #993 Fail to parsing PostgreSQL due to the quotation
8. ISSUE #1015 Support SQL like SELECT id, COUNT(*) FROM table GROUP BY 1,2
9. ISSUE #1120 Derived columns of GROUP BY / ORDER BY appear in query result
10. ISSUE #1186 Dead lock may occur on MEMORY_STRICTLY mode when get connection on concurrency environment
11. ISSUE #1265 RoundRobinMasterSlaveLoadBalanceAlgorithm throw an ArrayIndexOutOfBoundsException when AtomicInteger overflow

Sharding-JDBC

1. ISSUE #372 Reuse PreparedStatement cause cache of route result do not clean
2. ISSUE #629 Support transaction isolation on JDBC
3. ISSUE #735 Unexpected slave datasource routing result when using Round-robin load-balance algorithm in Mybatis
4. ISSUE #1011 Can't resolve placeholder in Spring Boot YAML configuration

New Features

Core

1. ISSUE #980 Support DCL

Sharding-Proxy

1. ISSUE #916 Support authorization
2. ISSUE #936 Support registry center

Enhancements

Core

1. ISSUE #935 Use YAML instead of JSON to store configurations in registry center
2. ISSUE #1004 Properties can configure for Sharding and Master-slave independent

Bug Fixes

Core

1. ISSUE #919 Inline expression with groovy may cause memory leak
2. ISSUE #1015 Support SQL like SELECT id, COUNT(*) FROM table GROUP BY 1,2

Sharding-JDBC

1. ISSUE #372 Reuse PreparedStatement cause cache of route result do not clean
2. ISSUE #993 Fail to parsing PostgreSQL due to the quotation
3. ISSUE #1011 Can't resolve placeholder in Spring Boot YAML configuration

Milestones

1. Sharding-Proxy launch. Support the use of Sharding-Sphere in the form of database to support for MySQL CLI and GUI client

New Features

1. ISSUE #290 Support batch INSERT statements
2. ISSUE #501 Support OR statement

Enhancements

1. ISSUE #608 Support the USE statement of MySQL
2. ISSUE #609 Support the SHOW statement of MySQL
3. ISSUE #610 Optimize the DQL that does not contain a table name
4. ISSUE #611 Support the DESC statement of MySQL
5. ISSUE #652 Support Spring Boot Starter 2.x
6. ISSUE #701 Support caching parsing results of SQL to improve performance
7. ISSUE #702 Support $->{..} as mark for inline expression
8. ISSUE #719 Support Spring bean namespace to inject key generator objects
9. ISSUE #720 Support Spring bean namespace to inject sharding algorithm objects
10. ISSUE #773 Support sharding and autoincrement primary key of INSERT statements without column names

Bug Fixes

1. ISSUE #628 Support data type jsonb for PostgreSQL
2. ISSUE #629 Support transaction isolation on JDBC
3. ISSUE #646 When aliases in SELECT ITEMS correspond to the real column names of GROUP BY or ORDER BY, there is no need to add columns
4. ISSUE #735 Unexpected slave datasource routing result when using Round-robin load-balance algorithm in Mybatis
5. ISSUE #806 SQL parse error with NOT IN
6. ISSUE #827 Fix endless loop for bad SQL like SELECT * FROM table WHERE id IN ()

功能提升

1. ISSUE #600 支持TCL

缺陷修正

1. ISSUE #522 读写分离Slave库不需要执行DDL语句
2. ISSUE #540 梳理并支持别名为关键字SQL
3. ISSUE #577 支持YAML配置换行