You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixesspring-projects#3696
* Add an internal logic into `KafkaMessageSource` to react properly for the
`ErrorHandlingDeserializer` configuration and re-throw `DeserializationException`
artembilan
added a commit
to artembilan/spring-integration
that referenced
this issue
Jul 26, 2023
Fixesspring-projects#3696
* Add an internal logic into `KafkaMessageSource` to react properly for the
`ErrorHandlingDeserializer` configuration and re-throw `DeserializationException`
* GH-3696: DeserializationEx support for KafkaMS
Fixes#3696
* Add an internal logic into `KafkaMessageSource` to react properly for the
`ErrorHandlingDeserializer` configuration and re-throw `DeserializationException`
* * Use `ErrorHandlingUtils` from `spring-kafka` to determine a `deserializer` from consumer properties
* Revise the test in favor of just single `await().untilAsserted()` -
no reason to wait for assignment or check for returned record.
We just need to be sure that `DeserializationException` is thrown eventually
Expected Behavior
Similar logic to the listener container - send deserialization exceptions to the error channel.
Current Behavior
User has to manually move past the bad record by setting the offset.
Context
The text was updated successfully, but these errors were encountered: