Skip to content

Conversation

@moonyoungCHAE
Copy link
Contributor

  • As-is
    • When a @KafkaListener is created with both @Topic and @TopicPartition, the listener consumes messages based on @TopicPartition.
    • When @RetryableTopic is added, retry topics are managed based on @Topic.
  • To-be
    • Creating a @KafkaListener with both @Topic and @TopicPartition is not allowed.

fixes #4170

@sobychacko
Copy link
Contributor

@moonyoungCHAE There are build failures on the PR - Are you able to see this? https://github.com/spring-projects/spring-kafka/actions/runs/19523082207/job/55890231401?pr=4172.

Can you also trace, what happens to the retryable topic when we only provide TopicPartition on the KafkaListener? Since there are no topics given any more on KafkaListener (based on this PR), will it still create destinations for retry?

Thanks!

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.

@KafkaListener with Both topics and topicPartitions Breaks @RetryableTopic

2 participants