I want to subscribe to email discussion and development
Take it easy. And FYI, maybe we could modify the internal of orchestration
without changing API of orchestration. When the refactoring of orchestration
finishes, API changes and behavior changes of callers comes.
Juan Pan
panj...@apache.org
Juan Pan(Trista), Apache ShardingSphere
On
I think this maybe not so hard, we can do this like follow.
1. Remove the old modules.
2. Rename the new modules.
3. Modify references we can easy find.
4.Follow the error lead.
—
Haisheng Sun (sunbufu)
Apache ShardingSphere
On 12/11/2019 16:14,guangyuan wang wrote:
The modifications
The modifications in sharding-orchestration are:
1. The RegistryCenter is changed to split into 3 interfaces: ConfigCenter,
Registry Center, DistributedLockManagement.
2. The related implementation class is changed and initialization is
changed.
These changes mean the sharding-orchestration module
Hi Yuan,
I’d like to join in discussion, however i have no idea about what is going now,
could you draft a workflow or schedule to give us a basic understanding about
it. Based on that, maybe others could give some great suggestion or idea.
Juan Pan
panj...@apache.org
Juan Pan(Trista),