The way avro works in the confluent ecosystem is that an identifier representing the schema is registered with the schema registry and embedded in the messages (by the producer's avro serializer) Consumers then use the identifier to lookup the exact schema used by the producer and use that to deserialize the remainder of the message so that's why the schema you're providing is being ignored.

@nicolas.estrada938 I think the problem is that you need to pass along the serde options to consumer constructor rather than the call to subscribe.

Yes I finally got it to work by passing in the :key-serde and :value-serde to the consumers... however I fail to grasp how one can subscribe to multiple topics with multiple value avro schemas with only one consumer. Thanks for your time 🙂

Well, yeah, the jackdaw avro serde API makes that a bit tricky. I'd probably just use confluent's generic avro serde and then unpack the GenericData using https://github.com/cddr/edn-avro. Not the most efficient (it incurs a JSON serialization/deserialization) but plays a bit nicer with the kafka/confluent ecosystem imo.

(i'm guilty of writing large chunks of each 😂)

Cool I'll check it out. Thanks! 🙂