redpanda-data / redpanda-data/connect
Add support for `NakWithDelay` for `nats_jetstream`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
When NATS messages are naked, they are going to be re-delivered immediately (see here, as described for the Backoff parameter, or here, directly in the NATS source code).
Sometimes is makes sense to wait a little before processing a message again, for example when it involves talking to another system and the network is down. In such a case, chances are good that the network is still down, when retrying immediately.
It would be very helpful to have support for NATS' NakWithDelay function and a configurable delay for the nats_jetstream input processor. That would allow to design processors who behave like "I can't process this message right now, please task me again in 1 minute or something".
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 locating the nats_jetstream input processor and its existing NAK handling, then read the linked NATS NakWithDelay API. Add a configurable redelivery delay and verify that messages can be scheduled for later retry rather than immediate redelivery, with tests covering the configured behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- stream-processing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100