MSK Connect Debezium Connector using AWS Glue Schema Registry for AVRO serialization

0

We are trying to integrate change data capture into our MSK cluster using the Debezium SQL Server plugin with AVRO serialization and AWS Glue Schema Registry. The connector appears to be working correctly as we can see the messages flowing into the Kafka topic and the AVRO schema is registered into our schema registry. However, when we attempt to deserialize the message from Kafka in a lambda function (MSK trigger), we are getting an error saying that the Schema cannot be found. We are using this library to do the AVRO serializaton/deserialization in both the connector and our lambda function. We've added some additional logging to the library and have found that the schema version id that gets written into the message during serialization is different than the one that gets pulled out of the message during deserialization. Has anyone successfully used Debezium with MSK connect and AWS Glue Schema registry? Pertinent configuration for our MSK connector is provided below:

  "key.converter": "org.apache.kafka.connect.storage.StringConverter",
  "key.converter.schemas.enable": "false",
  "key.converter.avroRecordType": "GENERIC_RECORD",
  "key.converter.region": "AWS_REGION",
  "key.converter.registry.name": "SCHEMA_REGISTRY_NAME",
  "key.converter.schemaAutoRegistrationEnabled": "true",
  "value.converter": "com.amazonaws.services.schemaregistry.kafkaconnect.AWSKafkaAvroConverter",
  "value.converter.schemas.enable": "true",
  "value.converter.avroRecordType": "GENERIC_RECORD",
  "value.converter.region": "AWS_REGION",
  "value.converter.registry.name": "SCHEMA_REGISTRY_NAME",
  "value.converter.schemaAutoRegistrationEnabled": "true",
asked 10 months ago62 views
No Answers

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions