I'm using Kafka Connect, and I'm trying to use the confluent compatible api from apicurio. I expect it should work with the confluent avro converter.
But I'm getting an error in the confluent library like: The given schema does not match any schema under the subject tst-kpn-des--reid-magic-byte-avro-key; error code: 40403 It's possible their is a bug in the confluent library, but just posting here for some direction.
I have a value and key schema on apicurio with content/global id of 1 and 2.
I was thinking maybe something canonical related is going on..? my next step was to look into the default setting on that within apicurio.
produce 4 byte magic byte style messages onto the topic
deploy kafka connect with connector configured as above
Expected vs Actual Behaviour
I expect it to successfully grab the schema. Totally possible I'm doing something very wrong. Hoping for some guidance.
Logs
Caused by: org.apache.kafka.common.errors.SerializationException: Error retrieving Avro key schema version for id 2
at io.confluent.kafka.serializers.AbstractKafkaSchemaSerDe.toKafkaException(AbstractKafkaSchemaSerDe.java:805)
at io.confluent.kafka.serializers.AbstractKafkaAvroDeserializer.schemaVersion(AbstractKafkaAvroDeserializer.java:222)
at io.confluent.kafka.serializers.AbstractKafkaAvroDeserializer.deserializeWithSchemaAndVersion(AbstractKafkaAvroDeserializer.java:269)
at io.confluent.connect.avro.AvroConverter$Deserializer.deserialize(AvroConverter.java:199)
at io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:126)
... 17 more
Caused by: io.confluent.kafka.schemaregistry.client.rest.exceptions.RestClientException: The given schema does not match any schema under the subject tst-kpn-des--reid-magic-byte-avro-key; error code: 40403
at io.confluent.kafka.schemaregistry.client.rest.RestService.sendHttpRequest(RestService.java:336)
at io.confluent.kafka.schemaregistry.client.rest.RestService.httpRequest(RestService.java:409)
at io.confluent.kafka.schemaregistry.client.rest.RestService.lookUpSubjectVersion(RestService.java:500)
at io.confluent.kafka.schemaregistry.client.rest.RestService.lookUpSubjectVersion(RestService.java:485)
at io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient.getVersionFromRegistry(CachedSchemaRegistryClient.java:353)
at io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient.getVersion(CachedSchemaRegistryClient.java:609)
at io.confluent.kafka.schemaregistry.client.CachedSchemaRegistryClient.getVersion(CachedSchemaRegistryClient.java:589)
at io.confluent.kafka.serializers.AbstractKafkaAvroDeserializer.schemaVersion(AbstractKafkaAvroDeserializer.java:204)
... 20 more
Description
Registry Version: 2.5.9.Final Persistence type: in-memory
I'm using Kafka Connect, and I'm trying to use the confluent compatible api from apicurio. I expect it should work with the confluent avro converter.
But I'm getting an error in the confluent library like:
The given schema does not match any schema under the subject tst-kpn-des--reid-magic-byte-avro-key; error code: 40403
It's possible their is a bug in the confluent library, but just posting here for some direction.I have a value and key schema on apicurio with content/global id of 1 and 2.
I was thinking maybe something canonical related is going on..? my next step was to look into the default setting on that within apicurio.
My config:
I produce messages onto my topic like:
Environment
Kubernetes: v1.26.15 Kafka Connect from Strimzi: 3.7.0 confluent avro converter: 7.6.1 confluent jdbc sink: 10.7.6
Steps to Reproduce
Expected vs Actual Behaviour
I expect it to successfully grab the schema. Totally possible I'm doing something very wrong. Hoping for some guidance.
Logs