spring-projects / spring-projects/spring-boot
Fail fast if a Kafka property is configured in spring.kafka.properties when a spring.kafka property could have been used instead
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
After upgraded to spring boot 3.1.0 configuration of kafka server via configuration property spring.kafka.properties.bootstrap.servers no longer working.
Always using default value localhost:9092 and therefore unable to connect.
Workaround to make it work is using configuration property spring.kafka.bootstrapServers but I don't think this is the intended way for configuration.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Kafka configuration using spring.kafka.properties.bootstrap.servers and compare it with spring.kafka.bootstrapServers. Trace the Spring Boot Kafka property binding entry point and make the configuration fail fast when the generic property duplicates a supported spring.kafka property, with an actionable error indicating the preferred property.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100