duansy123 commented on issue #23610:
URL:
https://github.com/apache/shardingsphere/issues/23610#issuecomment-1385233623
yes,it is in standalone mode,The following is the complete configuration
`databaseName: cxm_tenant_db
dataSources:
cxm_public:
url:
jdbc:mysql://xxxxxxxxx:3306/cxm_public?useUnicode=true&allowMultiQueries=true&characterEncoding=UTF-8&character_set_server=utf8mb4&connectionCollation=utf8mb4_bin&zeroDateTimeBehavior=convertToNull&useSSL=true&serverTimezone=Asia/Shanghai
username: root
password: root
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
minPoolSize: 1
ds0:
url:
jdbc:mysql://xxxxxxxxx:3306/cxm_agroup_0000?useUnicode=true&allowMultiQueries=true&character_set_server=utf8mb4&connectionCollation=utf8mb4_bin&zeroDateTimeBehavior=convertToNull&useSSL=true&serverTimezone=Asia/Shanghai
username: root
password: root
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
minPoolSize: 1
ds1:
url:
jdbc:mysql://xxxxxxxx:3306/cxm_agroup_0001?useUnicode=true&allowMultiQueries=true&character_set_server=utf8mb4&connectionCollation=utf8mb4_bin&zeroDateTimeBehavior=convertToNull&useSSL=true&serverTimezone=Asia/Shanghai
username: root
password: root
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
minPoolSize: 1
ds2:
url:
jdbc:mysql://xxxxxxxx3306/cxm_agroup_0002?useUnicode=true&allowMultiQueries=true&character_set_server=utf8mb4&connectionCollation=utf8mb4_bin&zeroDateTimeBehavior=convertToNull&useSSL=true&serverTimezone=Asia/Shanghai
username: root
password: root
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 50
minPoolSize: 1
# ds_1:
# url:
jdbc:mysql://127.0.0.1:3306/demo_ds_1?serverTimezone=UTC&useSSL=false
# username: root
# password:
# connectionTimeoutMilliseconds: 30000
# idleTimeoutMilliseconds: 60000
# maxLifetimeMilliseconds: 1800000
# maxPoolSize: 50
# minPoolSize: 1
rules:
- !SHARDING
tables:
research_info:
actualDataNodes: ds${0..2}.research_info
keyGenerateStrategy:
column: research_id
keyGeneratorName: snowflake
databaseStrategy:
standard:
shardingColumn: aid
shardingAlgorithmName: database_inline
company_info:
actualDataNodes: cxm_public.company_info
keyGenerateStrategy:
column: company_id
keyGeneratorName: snowflake
databaseStrategy:
none:
bindingTables:
none:
broadcastTables:
none:
# - t_order,t_order_item
defaultDatabaseStrategy:
standard:
shardingColumn: aid
shardingAlgorithmName: database_inline
defaultTableStrategy:
none:
# defaultAuditStrategy:
# auditorNames:
# - sharding_key_required_auditor
# allowHintDisable: true
shardingAlgorithms:
database_inline:
type: INLINE
props:
algorithm-expression: ds${aid % 3}
keyGenerators:
snowflake:
type: SNOWFLAKE
props:
worker-id: ${worker-id}
max-vibration-offset: 16
# auditors:
# sharding_key_required_auditor:
# type: DML_SHARDING_CONDITIONS
`
After I adjusted the default sharding strategy to none, it is now normal
So when the default sharding rule and the specified table do not participate
in the sharding configuration exist at the same time, it does not work in
version 5.3.1
--
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]
