I’m using the Debezium connector to monitor only a specific table (dbo.test_Cdc), but the connector is sending schema information for all tables in the database to Kafka. Despite my configuration settings, this results in the schema for the entire database being fetched instead of just the specific table, causing the connector to crash. Additionally, the connector doesn’t work without adding the schema.history.internal.kafka.topic parameter.
You probably need to set schema.history.internal.store.only.captured.tables.ddl=true in addition to the table include or exclude property. Once you set this property, you will be unable to add additional tables after the connection has been started, as their schema histories will not be found in the topic.
1 Like
Hello, could you help me elaborate my case? Thank for your time!
The original topic here is about how Debezium tracks database schemas internally, not a Kafka schema registry. Sorry @thawzinmyo, your issue is outside my area of expertise.
1 Like