Skip to content

Conversation

@artembilan
Copy link
Member

Fixes: #3555
Issue link: #3555

The batch might be processed in the @KafkaListener silently without looking into conversion failures header. So, that might cause in impression that nothing is wrong with the batch.

  • Mention KafkaHeaders.CONVERSION_FAILURES in the docs
  • Add warn for the failed conversion in the BatchMessagingMessageConverter
  • Some other code optimization clean up in the BatchMessagingMessageConverter

…LURES`

Fixes: spring-projects#3555
Issue link: spring-projects#3555

The batch might be processed in the `@KafkaListener` silently without looking into conversion failures header.
So, that might cause in impression that nothing is wrong with the batch.

* Mention `KafkaHeaders.CONVERSION_FAILURES` in the docs
* Add `warn` for the failed conversion in the `BatchMessagingMessageConverter`
* Some other code optimization clean up in the `BatchMessagingMessageConverter`
@artembilan artembilan requested a review from sobychacko November 1, 2024 16:48
@sobychacko sobychacko merged commit 0318c1d into spring-projects:main Nov 11, 2024
3 checks passed
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.

Log conversion failures in batch listeners

2 participants