Closed terrymanu closed 3 years ago
This exception is caused by the case that the removed read_ds_1
data source and the pr_ds
logical data source have the same table. The single table is checked by default when it is loaded.
After discussion, we decided to add an option to the single table conflict check logic, allowing users to decide whether to check or not.
Which version of ShardingSphere did you use?
master
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
Expected behavior
Update config successful
Actual behavior
original config in zk
changed config in zk
exception thrown