glon opened a new issue #10063: URL: https://github.com/apache/shardingsphere/issues/10063
> ShardingSphere Proxy 4.1.1 We get a problem when executing SQL like `select * from city;` , can't get the results. Table city configured in broadcastTables. ```sql > select * from city; Query OK, 0 rows affected, 25971 warnings (0.00 sec) > select count(*) from city; +----------+ | count(*) | +----------+ | 75331 | +----------+ 1 row in set (0.03 sec) ``` And other client returns with error like :  Our confi-sharding.yaml : ``` schemaName: shardingdb dataSources: ds_0: url: jdbc:mysql://10.13.63.17:3306/goods?useTimezone=true&serverTimezone=Asia/Shanghai&useSSL=false username: sharding_user password: 123456 connectionTimeoutMilliseconds: 30000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 ds_1: url: jdbc:mysql://10.13.63.97:3306/order?useTimezone=true&serverTimezone=Asia/Shanghai&useSSL=false username: sharding_user password: 123456 connectionTimeoutMilliseconds: 30000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 ds_2: url: jdbc:mysql://10.13.63.14:3306/partner?useTimezone=true&serverTimezone=Asia/Shanghai&useSSL=false username: sharding_user password: 123456 connectionTimeoutMilliseconds: 30000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 ds_3: url: jdbc:mysql://10.13.63.19:3306/common?useTimezone=true&serverTimezone=Asia/Shanghai&useSSL=false username: sharding_user password: 123456 connectionTimeoutMilliseconds: 30000 idleTimeoutMilliseconds: 60000 maxLifetimeMilliseconds: 1800000 maxPoolSize: 50 shardingRule: tables: # ds_0 test_good: actualDataNodes: ds_0.test_good # ds_1 test_order: actualDataNodes: ds_1.test_order # ds_2 test_partner: actualDataNodes: ds_2.test_partner # ds_3 test_common: actualDataNodes: ds_3.test_common broadcastTables: - Area - City defaultDatabaseStrategy: none: defaultTableStrategy: none: ``` -- 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]
