MINOR: Fix Streams DLQ config typo in upgrade guide#21551
Open
lelerabino wants to merge 1 commit intoapache:trunkfrom
Open
MINOR: Fix Streams DLQ config typo in upgrade guide#21551lelerabino wants to merge 1 commit intoapache:trunkfrom
lelerabino wants to merge 1 commit intoapache:trunkfrom
Conversation
### Problem
The Kafka Streams 4.2 upgrade guide documents the DLQ configuration as:
`errors.deadletterqueue.topic.name`
However the StreamsConfig constant defines the property as:
`errors.dead.letter.queue.topic.name`
This mismatch may lead users to configure the wrong property.
### Solution
Update the upgrade guide to use the correct configuration key.
### Scope
Documentation-only change. No functional impact.
chia7712
reviewed
Feb 24, 2026
| ### Other changes | ||
|
|
||
| Kafka Streams now supports Dead Letter Queue (DLQ). A new config `errors.deadletterqueue.topic.name` allows to specify the name of the DLQ topic. When set and `DefaultProductionExceptionHandler` is used, records that cause exceptions will be forwarded to the DLQ topic. If a custom exception handler is used, it is up to the custom handler to build DLQ records to send, hence, depending on the implementation, the `errors.deadletterqueue.topic.name` configuration may be ignored. `org.apache.kafka.streams.errors.ProductionExceptionHandler$ProductionExceptionHandlerResponse` is deprecated and replaced by `org.apache.kafka.streams.errors.ProductionExceptionHandler$Response`. Methods `handle` and `handleSerializationException` in `org.apache.kafka.streams.errors.ProductionExceptionHandler` are deprecated and replaced by `handleError` and `handleSerializationError` respectively in order to use the new `Response` class. More details can be found in [KIP-1034](https://cwiki.apache.org/confluence/x/HwviEQ). | ||
| Kafka Streams now supports Dead Letter Queue (DLQ). A new config `errors.dead.letter.queue.topic.name` allows to specify the name of the DLQ topic. When set and `DefaultProductionExceptionHandler` is used, records that cause exceptions will be forwarded to the DLQ topic. If a custom exception handler is used, it is up to the custom handler to build DLQ records to send, hence, depending on the implementation, the `errors.dead.letter.queue.topic.name` configuration may be ignored. `org.apache.kafka.streams.errors.ProductionExceptionHandler$ProductionExceptionHandlerResponse` is deprecated and replaced by `org.apache.kafka.streams.errors.ProductionExceptionHandler$Response`. Methods `handle` and `handleSerializationException` in `org.apache.kafka.streams.errors.ProductionExceptionHandler` are deprecated and replaced by `handleError` and `handleSerializationError` respectively in order to use the new `Response` class. More details can be found in [KIP-1034](https://cwiki.apache.org/confluence/x/HwviEQ). |
Member
There was a problem hiding this comment.
nice find. I have updated KIP as well
chia7712
approved these changes
Feb 24, 2026
mjsax
approved these changes
Feb 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Problem
The Kafka Streams 4.2 upgrade guide documents the DLQ configuration as:
However the StreamsConfig constant defines the property as:
This mismatch may lead users to configure the wrong property.
Solution
Update the upgrade guide to use the correct configuration key.
Scope
Documentation-only change. No functional impact.