You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the release of 5.1.2 version, we have received a lot of feedback from users and developers. Now we plan to release the ShardingSphere 5.2.0 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.
Scaling: Change keyword for part of data migration DistSQL
Scaling: Redesign part of data migration DistSQL
DistSQL: Unify parameter type specification
DistSQL: Split SHOW INSTANCE MODE to SHOW MODE INFO and SHOW INSTANCE INFO
DistSQL: Change DROP SCALING jobId to CLEAN MIGRATION jobId
DistSQL: Remove COUNT INSTANCE RULES
Add database found that high availability supports all the slave libraries to go offline, and the main library undertakes the read traffic configuration
SnowflakeKeyGenerateAlgorithm supports configuring worker-id in standalone mode
Replace sourceDataSourceName with productionDataSourceName in Shadow API Configuration
ShardingSphere metadata refactoring for splitting actual metadata and logical metadata
Use ConnectionContext, QueryContext to remove ThreadLocal in FetchOrderByValueQueuesHolder, TrafficContextHolder, SQLStatementDatabaseHolder and TransactionHolder
Modify the default value of the ShardingSphere-Proxy version in the helm chart
Docker container will exit if ShardingSphere-Proxy failed to startup
Helm Charts in ShardingSphere repository are transferred to sub-project shardingsphere-on-cloud
Scaling: Plenty of refactor for better code reuse
DistSQL: Add a new category named RUL
Refactor the schedule module and split it into cluster schedule and standalone schedule
Remove memory mode, keep standalone mode and cluster mode
Refactoring metadata table loading logic and persistence logic
Refactoring distributed locks to retain the most concise interface design
Refactor : Unify The Creation for Proxy Containers in IT from ENV Modules
Refactor : Unify The Configuration for container created by testcontainer
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Release 5.2.0
Hi community,
After the release of 5.1.2 version, we have received a lot of feedback from users and developers. Now we plan to release the ShardingSphere 5.2.0 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.
Mail: https://lists.apache.org/thread/rr474o9hk3nng6ty9cwtcxsr1vlvgrmc
Release Notes
New Feature
CREATE MIGRATION PROCESS CONFIGURATION
ALTER MIGRATION PROCESS CONFIGURATION
SHOW MIGRATION PROCESS CONFIGURATION
ADD MIGRATION SOURCE RESOURCE
SHOW SQL_TRANSLATOR RULE
CREATE SHARDING AUDITOR
ALTER SHARDING AUDITOR
SHOW SHARDING AUDIT ALGORITHMS
Enhancement
SHOW INSTANCE LIST
&SHOW INSTANCE INFO
EXPORT DATABASE CONFIG
FORMAT SQL
CREATE TRAFFIC RULE
writeDataSourceQueryEnabled
for RDL READWRITE_SPLITTING RULE.assistEncryptor
for Encrypt RDLCREATE SHARDING TABLE RULE
Bug Fix
SHOW SHARDING TABLE RULES
ALTER SHARDING TABLE RULE
ALTER RESOURCE
CREATE TRAFFIC RULE
failed when load balance algorithm is nullDistSQL
adding shadow algorithm exception without shadow data sourceAPI Changes
SHOW INSTANCE MODE
toSHOW MODE INFO
andSHOW INSTANCE INFO
DROP SCALING jobId
toCLEAN MIGRATION jobId
COUNT INSTANCE RULES
sourceDataSourceName
withproductionDataSourceName
in Shadow API ConfigurationRefactor
Beta Was this translation helpful? Give feedback.
All reactions