You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the system I'm working on, I have consumers connected to external topics using the non-blocking retry mechanism with @RetryableTopic. Currently, when I create the retry topic, I link the main topic to a retry name. These retry topics are generic and not specific to my consumer. I would like to configure a retry topic based on my consumer, considering that one flow may have executed successfully while another may not. Is there a way to achieve this? I've considered implementing the RetryTopicNamesProviderFactory interface, but I've struggled to obtain consumer-specific information based on the DestinationTopic.Properties.
I've also contemplated passing retrySuffix and dltSuffix information, but I'm uncertain if this is the best approach.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the system I'm working on, I have consumers connected to external topics using the non-blocking retry mechanism with
@RetryableTopic
. Currently, when I create the retry topic, I link the main topic to a retry name. These retry topics are generic and not specific to my consumer. I would like to configure a retry topic based on my consumer, considering that one flow may have executed successfully while another may not. Is there a way to achieve this? I've considered implementing theRetryTopicNamesProviderFactory
interface, but I've struggled to obtain consumer-specific information based on theDestinationTopic.Properties
.I've also contemplated passing
retrySuffix
anddltSuffix
information, but I'm uncertain if this is the best approach.Beta Was this translation helpful? Give feedback.
All reactions