Skip to content

Conversation

@Nikita-Shupletsov
Copy link
Contributor

@Nikita-Shupletsov Nikita-Shupletsov commented Oct 27, 2025

Updates Kafka Streams upgrade guide for 4.2.0 release.

Reviewers: Matthias J. Sax [email protected]

@github-actions github-actions bot added triage PRs from the community docs small Small PRs labels Oct 27, 2025
@mjsax mjsax added ci-approved streams and removed triage PRs from the community labels Nov 3, 2025
Copy link
Member

@mjsax mjsax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. Made a pass.

<p>
Kafka Streams now supports Dead Letter Queue (DLQ).
A new config <code>errors.deadletterqueue.topic.name</code> allows to specify the name of the DLQ topic. When set and <code>DefaultProductionExceptionHandler</code> 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, in this case, the <code>errors.deadletterqueue.topic.name</code> configuration has no impact.
Copy link
Member

@mjsax mjsax Nov 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if "has no impact" is the right phrase to use? -- Users can still access the config and use it, even if I understand that they need to write code for it.

Wondering if we should add something to the docs (separate PR, or just filing a Jira for now), explaining how to actually implement a customer handler correctly?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took the phrase from the kip: https://cwiki.apache.org/confluence/display/KAFKA/KIP-1034%3A+Dead+letter+queue+in+Kafka+Streams under public interfaces.

I will paraphrase it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mjsax mjsax merged commit 33ffe06 into apache:trunk Nov 5, 2025
18 of 21 checks passed
@mjsax
Copy link
Member

mjsax commented Nov 5, 2025

Thanks for the PR. Merged to trunk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants