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 }}
This repository has been archived by the owner on Nov 20, 2024. It is now read-only.
I am encountering issues with producing KTable outputs and have tried two approaches:
Using KTable as Output and Reading It as Input: getting error : java.lang.ClassCastException: class jdk.proxy2.$Proxy217 cannot be cast to class org.apache.kafka.kstream.KTable
Using KStream as Output and Reading It as KTable Input: getting error : Caused by: java.lang.ClassCastException: class org.apache.kafka.streams.kstream.internals.KStreamImpl cannot be cast to class org.apache.kafka.streams.kstream.KTable
if I change function return type from KTable to KStream for both input and output working without any issues (note: just changed the binder to kstreamBinder in cofnig for input and output , for KTable used ktableBinder)
Environment:
Spring Boot: 3.3.2
Spring Cloud Binder: 4.1.3
I have noticed that others have also experienced similar issues in the past:
Issue with Producing KTable Output
I am encountering issues with producing KTable outputs and have tried two approaches:
Using KTable as Output and Reading It as Input: getting error : java.lang.ClassCastException: class jdk.proxy2.$Proxy217 cannot be cast to class org.apache.kafka.kstream.KTable
Using KStream as Output and Reading It as KTable Input: getting error : Caused by: java.lang.ClassCastException: class org.apache.kafka.streams.kstream.internals.KStreamImpl cannot be cast to class org.apache.kafka.streams.kstream.KTable
if I change function return type from KTable to KStream for both input and output working without any issues (note: just changed the binder to kstreamBinder in cofnig for input and output , for KTable used ktableBinder)
Environment:
Spring Boot: 3.3.2
Spring Cloud Binder: 4.1.3
I have noticed that others have also experienced similar issues in the past:
GitHub Issue #1085
GitHub Pull Request #1105
The text was updated successfully, but these errors were encountered: