Skip to content

Add error topic deletion to clean up of consumer producer#417

Open
jkbe wants to merge 2 commits intomasterfrom
fix/consumer-producer-clean-error-topic
Open

Add error topic deletion to clean up of consumer producer#417
jkbe wants to merge 2 commits intomasterfrom
fix/consumer-producer-clean-error-topic

Conversation

@jkbe
Copy link
Member

@jkbe jkbe commented Feb 18, 2026

Currently, running the clean command for a KafkaConsumerProducerApplication does not delete the error topic.

@Builder.Default
@NonNull
Map<String, String> labeledOutputTopics = emptyMap();
String errorTopic;
Copy link
Member Author

Choose a reason for hiding this comment

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

Could this lead to any issues for producers? I wasn't able to spot any issues like that. KafkaProducerApplication simply doesn't set an errorTopic when building ProducerTopicConfig and therefore should be fine I think.

Copy link
Member

Choose a reason for hiding this comment

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

I am not sure here. I think it might be better to introduce a separate class here

Copy link
Member

Choose a reason for hiding this comment

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

I mean there is already ConsumerProducerTopicConfig?

Copy link
Member Author

@jkbe jkbe Feb 18, 2026

Choose a reason for hiding this comment

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

Yes, that class exists to collect all topic info of a ConsumerProducer but it has a method to then obtain a ProducerTopicConfig again so that ProducerCleanUpRunner can be used:

Are you suggesting to add an extra clean up runner in ConsumerProducerCleanUpRunner to clean up the error topic? That would keep the logic separate from the producer clean up.

Copy link
Member

Choose a reason for hiding this comment

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

Yes I think that makes more sense

@jkbe jkbe marked this pull request as ready for review February 18, 2026 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments