Default for spring.kafka.listener.missing-topics-fatal is no longer aligned with Spring Kafka's default #20917
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.
Related to:
ISSUE -20828
Issue Explanation:
Spring-Kafka configuration change - Starting with version 2.3.4, the missingTopicsFatal container property is false by default. (Previously) When this is true, the application fails to start if the broker is down; many users were affected by this change;
After this S-K config change, default for spring.kafka.listener.missing-topics-fatal is no longer aligned with Spring Kafka's default.
AIM:
Update the
missingTopicsFatal
default value to be consistent with above referenced Spring-Kafka changeThis commit contains:
KafkaProperties.java
updatemissingTopicsFatal
default value tofalse
.