spring-cloud / spring-cloud/spring-cloud-stream
Support customize message before sending to DLQ
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 646
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 8
Description
@Vsevolod123 commented on Wed Mar 24 2021
It would be nice to customize message before sending it to DLQ.
Use case:
Add some header x-retries to message before send it to DLQ with current value + 1 or 1 if current value is null. We can use this header to controll retries count.
Contributor guide
No contributing guide indexed for this repository
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 locating the dead-letter-queue handling entry point in Spring Cloud Stream and reviewing the related spring-cloud-stream-binder-kafka issue referenced in the message. Define how callers customize the message and how the x-retries header is updated, then add coverage showing the customized message reaches the DLQ.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka, spring
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100