-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support to infer kafka key and value deserializer types when batch is enabled #598
Add support to infer kafka key and value deserializer types when batch is enabled #598
Conversation
7659056
to
bcee29b
Compare
…nsumerRecords It looks like when using a batch listener with a parameter of List<ConsumerRecord<K,V>> the framework picks a List deserializer instead of looking at the ConsumerRecord type args. With this change, it will look at the type args of the ConsumerRecord to determine the kafka message deserializer
bcee29b
to
7805a2f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I patched one of my projects with your modifications and it runs flawlessly in production. 👍
Thanks !
Hi, is there any ETA when this change is being released? I am desperately looking to incorporate this change :-) Thanks in advance for an answer @graemerocher . |
Can we release this? #811 |
…nsumerRecords (#598) It looks like when using a batch listener with a parameter of List<ConsumerRecord<K,V>> the framework picks a List deserializer instead of looking at the ConsumerRecord type args. With this change, it will look at the type args of the ConsumerRecord to determine the kafka message deserializer
I ran into #502. Taking a stab at fixing it.
It looks like when using a batch listener with a parameter of List<ConsumerRecord<K,V>> the framework picks a List deserializer instead of looking at the ConsumerRecord type args. With this change, it will look at the type args of the ConsumerRecord to determine the kafka message deserializer
This should resolve #502