Skip to content

Commit f1ca2fd

Browse files
garyrussellartembilan
authored andcommitted
GH-2448: State Non-Blocking Retries API Status
Resolves #2448
1 parent ada628a commit f1ca2fd

File tree

2 files changed

+2
-6
lines changed

2 files changed

+2
-6
lines changed

spring-kafka-docs/src/main/asciidoc/retrytopic.adoc

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,8 @@
11
[[retry-topic]]
22
=== Non-Blocking Retries
33

4-
IMPORTANT: This is an experimental feature and the usual rule of no breaking API changes does not apply to this feature until the experimental designation is removed.
5-
Users are encouraged to try out the feature and provide feedback via GitHub Issues or GitHub discussions.
6-
This is regarding the API only; the feature is considered to be complete, and robust.
7-
84
Version 2.9 changed the mechanism to bootstrap infrastructure beans; see <<retry-config>> for the two mechanisms that are now required to bootstrap the feature.
95

10-
After these changes, we are intending to remove the experimental designation, probably in version 3.0.
11-
126
Achieving non-blocking retry / dlt functionality with Kafka usually requires setting up extra topics and creating and configuring the corresponding listeners.
137
Since 2.7 Spring for Apache Kafka offers support for that via the `@RetryableTopic` annotation and `RetryTopicConfiguration` class to simplify that bootstrapping.
148

spring-kafka-docs/src/main/asciidoc/whats-new.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,8 @@ See <<same-broker-multiple-tests>> for more information.
3232
[[x30-retryable]]
3333
==== Retryable Topics Changes
3434

35+
This feature is no longer considered experimental (as far as its API is concerned), the feature itself has been supported since 2.7, but with a greater than normal possibility of breaking API changes.
36+
3537
The bootstrapping of <<retry-topic>> infrastructure beans has changed in this release to avoid some timing problems that occurred in some application regarding application initialization.
3638
See <<retry-config>> for more information.
3739

0 commit comments

Comments
 (0)