[DISCUSS] Release Plan of ShardingSphere 5.3.2

[TeslaCN]

Release 5.3.2

Hi community,

After the release of 5.3.1 version, we have received a lot of feedback
from users and developers. Now we plan to release the ShardingSphere 5.3.2
version these days, which has made a lot of optimization and improvement for
these feedback.

Please refer to this release notes to confirm whether it contains the
features you expect. If I missed anything, please remind me ASAP. If there
are any suggestions, please feel free to tell us.

Release Notes

API Changes

1. Proxy: Add property system-log-level, support dynamic change of log level by DistSQL.
2. DistSQL: Remove Hint-related DistSQL, users can use SQL Hint instead

New Features

1. Scaling: Support any type of column unique key table

Enhancements

1. Scaling: Use stream query for inventory dump and data consistency check
2. Scaling: Compatible with VARBINARY column type in MySQL binlog parsing
3. Scaling: Refactor AbstractSimplePipelineJob.execute to blocking
4. Scaling: Improve table records count calculation
5. Scaling: Support proxy sharding rule absent for migration job
6. Scaling: Add useServerPrepStmts=false for pipeline job on MySQL
7. Scaling: Improve datetime/time parsing for MySQL binlog
8. Scaling: Add global status for prepare stage
9. Scaling: Add netTimeoutForStreamingResults for pipeline job on MySQL
10. Authority: Support specifying password authentication method
11. Authority: Add md5 authentication support for openGauss protocol
12. Agent: Add more metrics for JDBC
13. Kernel: ShardingSphere Driver configuration supports Apollo
14. Kernel: Adjust SKIP_ENCRYPT_REWRITE SQL Hint to SKIP_SQL_REWRITE to support more scenarios
15. Kernel: Support openGauss EXPLAIN PERFORMANCE
16. Encrypt: Like supports concat function

Bug Fixes

1. Scaling: Fix unicode char and special char decoding for PostgreSQL incremental task
2. Scaling: Fix Migration not support PostgreSQL json type
3. DistSQL: CREATE SHARDING TABLE RULE supports NONE strategy
4. Kernel: Fix use system database error when data sources are empty
5. Kernel: Fix set worker-id does not take effect with Standalone mode
6. Kernel: Clear storage node information when delete readwrite-splitting and database discovery rules
7. Kernel: Fix the abnormal problem of Column index out of range in single table complex query
8. Kernel: Fix PostgreSQL like lower case failed.
9. Kernel: Fixed the exception of built-in metabase data collection when the front and back database types were inconsistent
10. Kernel: Fix the problem of routing error reporting under certain table names
11. Kernel: Fix MySQL create procedure parse error
12. Kernel: Fix union extract table name NPE
13. Kernel: Fix upper case table constraint not rewrite error
14. Kernel: Fix failed to parse PostgreSQL / openGauss SQL contains money type
15. Kernel: Fix PostgreSQL / openGauss positional parameter rule
16. Kernel: Fix PostgreSQL / openGauss failed to parse const with type cast
17. Kernel: Fix Chinese characters encode exception when execute select with sql federation engine
18. Kernel: Fix IndexOutOfBoundsException when execute set variable statement int jdbc adapter
19. Kernel: Fix index does not exist exception when execute drop index statement
20. Proxy: Properly handle number sign in MySQL Proxy binary protocol
21. Proxy: Fix PostgreSQL Proxy failed to handle bytea data type
22. Proxy: Fix PostgreSQL Proxy failed to parse time value with microseconds
23. Proxy: Fix PostgreSQL protocol codec for date type in binary format
24. Proxy: Fix possible CCE PostgreSQLInt2BinaryProtocolValue
25. Proxy: Fix possible error when client pass quoted charset to PostgreSQL/openGauss Proxy

[zhfeng]

Thanks for a new release and I'd like to add the following features for helping quarkus-shardingsphere-jdbc in native support:

• Refactor YamlLoggingRuleConfigurationSwapper to add getDefaultLoggingRuleConfiguration  #24728
• Refactor LoggingUtils to move out codes related to logback #24727
• Add jandex-maven-plugin to generate idx for classes #24726

[zhfeng]

And

• Upgrade groovy to 4.0.10 #24732

[zhfeng]

@TeslaCN is there any release schedule I can check?

[zhfeng]

It is not an exact date and just like we are planning to release 5.3.3 in June.

[TeslaCN]

Thanks for your suggestion. We will make a plan soon.

[TeslaCN]

We have set deadline for milestone. https://github.com/apache/shardingsphere/milestones

[zhfeng]

Thanks a lot @TeslaCN and it is much clearer now!

Also, it is possible to add above four issues in 5.3.2? They are all really helpful to quarkus-shardingsphere-jdbc in native building.

[TeslaCN]

Thanks a lot @TeslaCN and it is much clearer now!

Also, it is possible to add above four issues in 5.3.2? They are all really helpful to quarkus-shardingsphere-jdbc in native building.

I cannot come to a decision about this. Please @terrymanu @tristaZero help checking this.