fengchao-GitHub opened a new issue #9218:
URL: https://github.com/apache/shardingsphere/issues/9218
version: sharding proxy 5.0.0
yml:
schemaName: sharding_db
dataSourceCommon:
username: root
password: 123456
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
minPoolSize: 1
maintenanceIntervalMilliseconds: 30000
dataSources:
ds1:
url:
jdbc:mysql://192.168.255.115/testdb1?serverTimezone=UTC&useSSL=false&characterEncoding=utf8
ds1_slave:
url:
jdbc:mysql://192.168.255.116/testdb1?serverTimezone=UTC&useSSL=false&characterEncoding=utf8
ds2:
url:
jdbc:mysql://192.168.255.115/testdb2?serverTimezone=UTC&useSSL=false&characterEncoding=utf8
ds2_slave:
url:
jdbc:mysql://192.168.255.116/testdb2?serverTimezone=UTC&useSSL=false&characterEncoding=utf8
rules:
- !SHARDING
tables:
t_order:
actualDataNodes: ms_ds${1..2}.t_order${1..2}
databaseStrategy:
standard:
shardingColumn: uid
shardingAlgorithmName: database_inline
tableStrategy:
standard:
shardingColumn: id
shardingAlgorithmName: t_order_inline
keyGenerateStrategy:
column: id
keyGeneratorName: snowflake
bindingTables:
- t_order
broadcastTables:
- t_user
- t_org
defaultDatabaseStrategy:
none:
defaultTableStrategy:
none:
shardingAlgorithms:
database_inline:
type: INLINE
props:
algorithm-expression: ms_ds${uid % 2+1}
t_order_inline:
type: INLINE
props:
algorithm-expression: t_order${order_id % 2+1}
keyGenerators:
snowflake:
type: SNOWFLAKE
props:
worker-id: 123
- !REPLICA_QUERY
dataSources:
ms_ds1:
primaryDataSourceName: ds1
replicaDataSourceNames:
- ds1_slave
loadBalancerName: ROUND_ROBIN
ms_ds2:
primaryDataSourceName: ds2
replicaDataSourceNames:
- ds2_slave
loadBalancerName: ROUND_ROBIN
##############################################
*** when I try to connect the proxy db it misreport:
10002 _ 2Unknown exception [Can not route tables for '[ENGINES]', please
make sure the tables are in same schema.]

----------------------------------------------------------------
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]