The Compose file configures the Connect service to use the default (de-)serializers for the Connect instance and starts one additional service, the Confluent schema registry. To do this, follow the same steps above for MySQL but instead using the docker-compose-mysql-avro-connector.yaml and register-mysql-avro.json configuration files. Debezium Connector configurationĬonfiguring Avro at the Debezium Connector involves specifying the converter and schema registry as a part of the connectors configuration. The Compose file configures the Connect service to use the Avro (de-)serializers for the Connect instance and starts one more additional service, the Confluent schema registry. Kafka Connect Worker configurationĬonfiguring Avro at the Kafka Connect worker involves using the same steps above for MySQL but instead using the docker-compose-mysql-avro-worker.yaml configuration file instead. Using Avro in conjunction with the schema registry allows for much more compact messages. In the Kafka Connect worker configuration or in the connector configuration. To use Avro-style messages instead of JSON, # Modify records in the database via MySQL clientĭocker-compose -f docker-compose-mysql.yaml exec mysql bash -c 'mysql -u $MYSQL_USER -p$MYSQL_PASSWORD inventory ' # Shut down the clusterĭocker-compose -f docker-compose-mysql.yaml down Using MySQL and the Avro message format ![]() # Start the topology as defined in export DEBEZIUM_VERSION=1.9ĭocker-compose -f docker-compose-mysql.yaml upĬurl -i -X POST -H "Accept:application/json " -H "Content-Type:application/json " -d Consume messages from a Debezium topicĭocker-compose -f docker-compose-mysql.yaml exec kafka /kafka/bin/kafka-console-consumer.sh \
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |