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
When using KafkaListener on class level, and configuring non blocking retry with RetryTopicConfiguration, records should go to the retry topic, when failed by exception set as non blocking exceptions.
As stated in the documentation, this functionality is not supported.
"At this time this functionality doesn’t support class level @KafkaListener annotations."
We need this functionality especially when listeners are on class level, with KafkaHandlers handling different payloads. The reason is, if one type of payload fails, we would still be able to process, the other types. Today we can either fail the message completely, or using blocking retry, which will stop processing of all types of payload.
Workaround could be having each payload on separate topics. But this breaks our topic strategy.
The text was updated successfully, but these errors were encountered:
…n class level
Fixes: spring-projects#3012
* Non-blocking retries support `@KafkaListener` on class level, include `@RetryableTopic`, `@DltHandler`, `RetryTopicConfiguration`, `RetryTopicConfigurationSupport`.
* Doc and test Non-blocking retries support @KafkaListener on class level.
…n class level
Fixes: spring-projects#3012
* Non-blocking retries support `@KafkaListener` on class level, include `@RetryableTopic`, `@DltHandler`, `RetryTopicConfiguration`, `RetryTopicConfigurationSupport`.
* Doc and test Non-blocking retries support @KafkaListener on class level.
Wzy19930507
added a commit
to Wzy19930507/spring-kafka
that referenced
this issue
Mar 17, 2024
…n class level
Fixes: spring-projects#3012
* Non-blocking retries support `@KafkaListener` on class level, include `@RetryableTopic`, `@DltHandler`, `RetryTopicConfiguration`, `RetryTopicConfigurationSupport`.
* Doc and test Non-blocking retries support @KafkaListener on class level.
Fixes: #3012
* Non-blocking retries support for `@KafkaListener` on class level, which includes `@RetryableTopic,` `@DltHandler,` `RetryTopicConfiguration,` and `RetryTopicConfigurationSupport.`
* Doc and test for Non-blocking retries support for @KafkaListener on class level.
* Addressing PR review.
See these earlier related PRs:
#3112#3107
When using KafkaListener on class level, and configuring non blocking retry with RetryTopicConfiguration, records should go to the retry topic, when failed by exception set as non blocking exceptions.
As stated in the documentation, this functionality is not supported.
"At this time this functionality doesn’t support class level @KafkaListener annotations."
We need this functionality especially when listeners are on class level, with KafkaHandlers handling different payloads. The reason is, if one type of payload fails, we would still be able to process, the other types. Today we can either fail the message completely, or using blocking retry, which will stop processing of all types of payload.
Workaround could be having each payload on separate topics. But this breaks our topic strategy.
The text was updated successfully, but these errors were encountered: