Hi community,
This email is for the discussion about refactoring `OrchestrationShardingSphereDataSource` [1]. Why do we have to deal with this job? Here are some primary reasons, 1. Improve the efficiency of all the `renew()` functions. 2. Keep the same logic handling about `Orchestration` with `OrchestrationShardingProxy` However, the pros always come with the cons. The serious con here is the API change for `OrchestrationShardingSphereDataSource` with the Spring framework. I know it is a dilemma for us. But considering there have been many significant API changes for rules, I suppose it is definite that users have to face this whole new configuration look. Furthermore, I'd like to listen to your voice about this issue. [1] https://github.com/apache/shardingsphere/issues/7029 Cheers, Trista Juan Pan (Trista) Senior DBA & PMC of Apache ShardingSphere E-mail: [email protected]
