Open lsegv opened 1 hour ago
Thank you for reporting an issue!
Pinging @carlesarnal to respond or triage.
I can provide more details but i'm limited to what i can upload to public internet. So ask whatever you'll need to reproduce this (i've created a similar issue before with more context).
I've tested the avros own serialization and it handles this just fine, as soon as i let apicurio kafka library to deal with it it fails to parse it.
Most interesting is that at runtime during debug stage i can see that it have managed to resolve all the types from schema registry but fails to understand that T1 is a known type and fails to parse Msg schema (even though all the data is actually correct) i believe its a namespace resolution issue. The deserializer needs to handle namespaces correctly.
Examples in repository are using GenericType... which is pointless in java. Most people will want to use specific types.
So lets define a message type which will allow us to send multiple messages to the same topic without doing custom serialization hacks.
Try to send this type via kafka and deserialize it successfully on the other end. Without using generic records, we want specifically to parse instance of Msg so we can figure out what the contents are and handle accordingly.