Skip to content

Fix typos #3992

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 7, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ public void listen(Thing thing) {

Starting with version 3.3, Ignoring empty batches that result from filtering by `RecordFilterStrategy` is supported.
When implementing `RecordFilterStrategy`, it can be configured through `ignoreEmptyBatch()`.
The default setting is `false`, indicating `KafkaListener` will be invoked even if all `ConsumerRecord` s are filtered out.
The default setting is `false`, indicating `KafkaListener` will be invoked even if all ``ConsumerRecord``s are filtered out.

If `true` is returned, the `KafkaListener` [underline]#will not be invoked# when all `ConsumerRecord` are filtered out.
However, commit to broker, will still be executed.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -558,7 +558,7 @@ Previously, the listener had to echo custom correlation headers.
[[exchanging-messages]]
=== Request/Reply with `Message<?>`+++s+++

Version 2.7 added methods to the `ReplyingKafkaTemplate` to send and receive `spring-messaging` 's `Message<?>` abstraction:
Version 2.7 added methods to the `ReplyingKafkaTemplate` to send and receive ``spring-messaging``'s `Message<?>` abstraction:

[source, java]
----
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ public RetryTopicConfiguration myRetryTopic(KafkaTemplate<String, MyPojo> templa
}
----

NOTE: The default is having no timeout set, which can also be achieved by providing -1 as the timout value.
NOTE: The default is having no timeout set, which can also be achieved by providing -1 as the timeout value.

[[retry-topic-ex-classifier]]
== Exception Classifier
Expand Down Expand Up @@ -250,9 +250,9 @@ Starting with version 3.0.9, you can override the `RetryTopicConfigurationSuppor
[source, java]
----
@Override
protected Consumer<DeadLetterPublishingRecovererFactory>
protected Consumer<DeadLetterPublishingRecovererFactory>
configureDeadLetterPublishingContainerFactory() {

return (factory) -> factory.setDeadLetterPublisherCreator(
(templateResolver, destinationResolver) ->
new CustomDLPR(templateResolver, destinationResolver));
Expand Down