fix: retry lookup supports regex#21
Merged
BorekZnovustvoritel merged 1 commit intomainfrom Apr 9, 2026
Merged
Conversation
* handle sendErrors Signed-off-by: Marek Szymutko <mszymutk@redhat.com>
kosciCZ
approved these changes
Apr 9, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously the retry-topic lookup had to match the configured listener topic name exactly. However our usecase also includes using regexes, so the lookup has to support them in order to find the correct retry topic. Also handles SendErrors on retry sending.
I found out these issues exist in the library while working on ISV-7020. These changes resolved all issues I experienced when testing our consumer service locally, even with large messages being sent to retry topics.