Comven opened a new issue, #12742:
URL: https://github.com/apache/shardingsphere/issues/12742
shardingsphere-jdbc-core-spring-boot-starter-5.0.0-beta
The historical database contains tens of thousands of tables，Because the
order table is divided by day，When the program starts, the component of
shardingsphere auto executes the following SQL like
```
SELECT TABLE_NAME, COLUMN_NAME, DATA_TYPE, CLOLUMN_KEY, EXTRA,
COLLATION_NAME FROM information_schema.columns WHERE TABLE_SCHEMA='hist_db' AND
TABLE_NAME NOT IN('order_20210101','order_20210102',......
```
and SQL
```
SELECT FULL TABLES FROM 'hist_db' LIKE 'xxxx_yyy_20190610'
```
It takes a lot of time to execute these SQL to initialize the components of
shardingsphere after the program starts. The greater the number of sub tables,
the longer the time it takes to get stuck.
Is there any way to skip this step or speed it up ?
--
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]
