jiang-wei opened a new issue #9792: URL: https://github.com/apache/shardingsphere/issues/9792
## 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-alpha ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? SS-jdbc ### Expected behavior apply default non-sharding policy for newly created tables ### Actual behavior "Cannot route table for xxx, please make sure the tables are in the same schema" ### Reason analyze (If you can) configured two datasources in spring boot. one for liquibase & the other for hibernate & SS they are both created and liquibase needs some time to create the tables. Once tables created, SS complains "cannot route" for the newly created table ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. 1. create a table directly in the database, not through SS 2. query that table ### Example codes for reproduce this issue (such as a github link). link: #9782 -- 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. For queries about this service, please contact Infrastructure at: [email protected]
