redpanda-data / redpanda-data/connect
ACK SQS message if the S3 input object does not exist
Open
Nobody has claimed this yet.
enhancement
inputs
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
Add the ability to ACK the SQS message when S3 input object is not present, to catch error:
Failed to read message: NoSuchKey: The specified key does not exist.\n\tstatus code: 404
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 SQS acknowledgment handling and the S3 input read path in the Go code, then reproduce the reported NoSuchKey 404 case. Done means an SQS message is acknowledged when its S3 input object is absent, while other read failures retain their existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, stream-processing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100