Glowdable opened a new issue, #16880: URL: https://github.com/apache/shardingsphere/issues/16880
why did we need SingleTableRule? It's good feature for beginner. But It's too bad for production that people can not limit its influence.More seriously It‘s too slow when loading the metadata of all my tables. The ShardingSphere is a componentized design so I can only use read write spilt functionality, But it still loads the metadata of all my tables. That's totally unnecessary.This is the case. First, the application configure the default database where I can find the none sharding table Second , the ShardingSphere only load the configured sharding tables Third, the application sent a sql that did not contain the sharding table Forth，the ShardingSphere is going to load the table from the default database now，if can not find the table，return 'Not Found'; else found the table , can put it into cache as SingleTableRule, then return the result. At last，the ShardingSphere maybe can provide a way to disable SingleTableRule functionality instead of making it a default -- 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]
