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
{{ message }}
Repository navigation
Ability use different consume and produce types for the key and value #175
I don't think it's possible to use ParallelStreamProcessor with Consumer and Producer that do not share the same KeyType and ValueType.
Can this be considered in the future ?
changed the title [-]Ability to use ParallelStreamProcessor with different consume and produce types[/-][+]Ability use different consume and produce types for the key and value[/+]on Aug 2, 2022
Activity
astubbs commentedon Oct 19, 2021
Oh my! Yes! This is a breaking issue for the poll and produce use case. I will look into it with priority. Too much testing with just String types :)
BDeus commentedon Jan 31, 2022
Hi,
i see that you remove the blocker label.
Do you think the 1.0 version won't break after the implementation of the fix ?
astubbs commentedon Feb 1, 2022
Whoops - mistake :) Still plan on changing this. Will be resuming work on PC this week :)
astubbs commentedon Apr 12, 2022
Btw, workaround is to use your own instance of a producer to send a result back to Kafka, of any type.
astubbs commentedon Apr 12, 2022
Or use a more abstract type for your registered serde like a byte serde or string serde and use the serdes manually.
[-]Ability to use ParallelStreamProcessor with different consume and produce types[/-][+]Ability use different consume and produce types for the key and value[/+]johnbyrnejb commentedon Jul 7, 2023
Closing Issue