apache / apache/incubator-seata

seata 在读取yml 配置时驼峰命令的问题

Open
#2,334 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
26k
Forks
8.8k
Avg merge
1d 8h
Merged PRs (30d)
4

Description

我的环境是
JDK1.8
SpringBoot-2.1.8.RELEASE
SpringCloud-Greenwich.SR3
seata-server-1.1
seata-spring-boot-starte-1.1
以下是配置文件:
seata:
tx-service-group: my_test_tx_group
enable-auto-data-source-proxy: true
application-id: ${spring.application.name}
config:
type: springCloudConfig
service:
disable-global-transaction: false
vgroup-mapping:
my_test_tx_group: default
grouplist:
default: 127.0.0.1:8091
enable-degrade: false
registry:
type: eureka
eureka:
application: default
service-url: http://localhost:1001/eureka
weight: 1
错误日志为:
no available service 'null' found, please make sure registry config correct
获取的配置参数key:seata.service.vgroup-mapping.my_test_tx_group
实际在yml中的配置为:seata.service.vgroupMapping.my_test_tx_group
![image](https://user-images.githubusercontent.com/10000663/75679728-252c5400-5ccb-11ea-9e0a-0c2b2f8353c2.png)

Contributor guide

Open the contributing guide

Research direction

Start by tracing how the Seata Spring Boot configuration reads the YAML key seata.service.vgroup-mapping.my_test_tx_group and compare it with the reported bound key seata.service.vgroupMapping.my_test_tx_group. Check the configuration handling around vgroupMapping and reproduce the reported no available service 'null' error with the environment and YAML shown. Done means the configured group resolves to default and the service is found.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.