[FEATURE] When the message is unack(reject or nack with requeue=false), it is delivered to the dead letter queue

Open
#866 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
backend

Research direction

Start with AmqpMultiBundlesChannel and trace the existing message acknowledgement flow. Inspect how reject and nack APIs are represented, then verify the expected behavior for requeue=false. Done means both APIs are implemented and rejected or negatively acknowledged messages with requeue=false are delivered to the dead letter queue.

Written by the indexing model from the issue text.

Description

type/feature

The reject and nack apis need to be implemented in the AmqpMultiBundlesChannel

Dominant language
Java
Stars
123
Forks
41
Avg merge
4h 43m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from streamnative/aop

All issues in streamnative/aop

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.