spring-cloud / spring-cloud/spring-cloud-bus
SCB dependency sets (de)serializers to ByteArray if (de)serializers are set via config files (same as #248)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 445
- Forks
- 246
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 5
Description
This is a duplicate bug to the unresolved one from here, with same context and behavior as described there.
While the person from that thread resolved their problem through manually setting the kafka configs in code, I don't think that is the proper solution to go forward with. Setting kafka configs through property files shouldn't be overwritten by an external library.
To confirm, this also happens without bus, but with the spring cloud stream kafka binder only.
org.springframework.cloud:spring-cloud-starter-bus-kafka -> 3.1.2
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 reviewing the unresolved context in issue #248 and reproduce the behavior with spring-cloud-starter-bus-kafka 3.1.2 configured through property files. Compare it with the Spring Cloud Stream Kafka binder without Bus. Done means configured Kafka serializers are no longer overwritten and remain usable without manually setting them in code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka, spring-boot
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100