![]() The reported error was .errors.DataException: is not a valid field name. Note that the MongoDB document is not as fields in the Kafka message, but instead everything is in the payload as a string field as escaped JSON.ĭebezium does provide a Single Message Transform (SMT) to flatten the MongoDB record out like this, but in using it I hit a bug ( DBZ-649) that seems to be down to the MongoDB collection documents having different fields between documents. "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),Ĭheck /var/log/mongodb/mongod.log, should see replica set config success and oplog get created: T13:12:26.007+0000 I REPL replSetInitiate admin command received from client "clusterTime" : Timestamp(1520428346, 1), Starting in MongoDB 4.4.1, installing MongoDB via brew also installs the MongoDB Database Tools. Using a default configuration for the set", Optionally, also set the bindIp so that it listens on all IPs, not just loopback: net: But they worked for me :) Feel free to post in comments if I’m doing something wrong MongoDB config - enabling replica setsįor Debezium to be able to stream changes from MongoDB, Mongo needs to have replication configured:ĭocs: Replication / Convert a Standalone to a Replica SetĪdd replica set config to /etc/nf: replication: These steps may or may not be appropriate and proper. ![]() In Mongodb, Debezium, Kafka Connect, Apache Kafka, Replica Set at ĭisclaimer: I am not a MongoDB person. Streaming Data from MongoDB into Kafka with Kafka Connect and Debezium
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |