-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 5.2.1 have problem for init #21646
Comments
|
@AaronW-BE <dependency>
<groupId>org.yaml</groupId>
<artifactId>snakeyaml</artifactId>
<version>1.33</version>
</dependency> |
@MrXionGe Got it, Thanks a lot |
I get the this error after upgrading snakeyaml to 1.33:
This is my config: # shardingsphere 5.3.0文档 https://shardingsphere.apache.org/document/current/cn/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/
dataSources:
db0: # 单数据库节点无意义,当存在多个时用于区分
dataSourceClassName: com.zaxxer.hikari.HikariDataSource # 数据库连接池全类名
driverClassName: ${spring.datasource.driver-class-name}
jdbcUrl: ${spring.datasource.url}
username: ${spring.datasource.username}
password: ${spring.datasource.password}
props:
sql-show: true
rules:
- !SHARDING
broadcastTables: t_alarm_domain # 广播表规则列表
bindingTables: # 绑定表规则列表。见: https://github.com/apache/shardingsphere/issues/21002
- t_alarm,t_sensor_alarm
- t_alarm,t_video_alarm
- t_alarm,t_device_offline_alarm
- t_alarm,t_alarm_handle
tables: # 单分片键的标准分片场景
t_alarm:
actualDataNodes: db0.t_alarm_$->{2022..2025}
tableStrategy:
standard:
shardingColumns: alarm_time
shardingAlgorithmName: time-inline
t_sensor_alarm:
actualDataNodes: db0.t_sensor_alarm_$->{2022..2025}
tableStrategy:
standard:
shardingColumns: alarm_time
shardingAlgorithmName: time-inline
t_video_alarm:
actualDataNodes: db0.t_video_alarm_$->{2022..2025}
tableStrategy:
standard:
shardingColumns: alarm_time
shardingAlgorithmName: time-inline
t_device_offline_alarm:
actualDataNodes: db0.t_device_offline_alarm_$->{2022..2025}
tableStrategy:
standard:
shardingColumns: alarm_time
shardingAlgorithmName: time-inline
t_alarm_handle:
actualDataNodes: db0.t_alarm_handle_$->{2022..2025}
tableStrategy:
standard:
shardingColumns: alarm_time
shardingAlgorithmName: time-inline
shardingAlgorithms:
time-inline:
type: CLASS_BASED
props:
strategy: standard
algorithmClassName: cn.com.asoco.alarm_platform.server.sharding.AlarmTimeShardingAlgorithm # 使用自定义类实现分片逻辑处理
I don't know why... I was frustrated by the succession of problems I was having. Can anyone help me? |
broadcastTables:
- t_alarm_domain |
The exception logs following:
In class
ShardingSphereYamlConstructor
its do have a not exist methodsetCodePointLimit
in line 44The text was updated successfully, but these errors were encountered: