zhouyouwei-0127 opened a new issue #16180: URL: https://github.com/apache/shardingsphere/issues/16180
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? 5.0.0 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior After starting the agent, should be able to see the newly created or deleted tables ### Actual behavior can't see the newly created or deleted tables if don't restart the proxy ### Reason analyze (If you can) the proxy cached the table structure and not update when the table structure changed in actual datasource ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. config server.yaml:  readwrite-splitting.yaml:  table strcture in actual datasource:  table strcture in proxy:  when I create a table in the actual datasource like this  excute 'show tables' in proxy again,I can't see the change of table structure, but Ican query the data of the new tableļ¼  ### Example codes for reproduce this issue (such as a github link). -- 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]
