-
Notifications
You must be signed in to change notification settings - Fork 336
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
### Motivation Follow [pulsar#6449](apache/pulsar#6449) to support retry letter topic in go client ### Modifications - Add `retryRouter` for sending reconsume messages to retry letter topic - Add `ReconsumeLater(msg Message, delay time.Duration)` to Consumer interface - Add configureable retry letter topic name in `DLQPolicy` ```go type DLQPolicy struct { // ... // Name of the topic where the retry messages will be sent. RetryLetterTopic string } ``` enable it explicitly while creating consumer, default unenable ```go type ConsumerOptions struct { // ... // Auto retry send messages to default filled DLQPolicy topics RetryEnable bool } ``` - Add 2 `TestRLQ*` test cases
- Loading branch information
Showing
12 changed files
with
521 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.