hua74ni commented on issue #26012: URL: https://github.com/apache/shardingsphere/issues/26012#issuecomment-1580152252
> Then this is the problem, ShardingSphere scans the metadata and persists it, but if you do not execute DDL through ShardingSphere, it means that you have not notified ShardingSphere to make changes. > > If so, it is recommended to deploy a proxy to execute the DDL, or execute the REFRESH DistSQL through proxy. If there is no Proxy, you can only delete the data in zk, but this may cause configuration loss, which is not recommended. > > > > Hi @hua74ni Did you execute `ALTER TABLE` statement through ShardingSphere-JDBC? > > > > > > Not executed through ShardingSphere-JDBC（Business projects do not execute `ALTER TABLE` normally）, Execute `ALTER TABLE` directly in MySQL, Then restart the service All right, I think When the instance starts, it will check whether the zk metadata table and the actual mysql table DDL are consistent, and whether the inconsistency is consistent or needs to be persisted -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
