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 …

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…

Hello, could you help me elaborate my case? Thank for your time! [image] Deploy Schema Registry on DOKS(Kubernetes on DigitalOcean) Schema Registry Hello Contributors, Current Working Setup Kafka cluster (DigitalOcean) Kafka Connect (using Debezium and Outbox pattern) K…

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.

Debezium Connector: Filtering Specific Tables and Preventing Schema History for All Tables

Kafka Connect

thawzinmyo 2 April 2025 09:28 3

Hello, could you help me elaborate my case? Thank for your time!

Topic		Replies	Views
Issues with Debezium SQL Server Connector and KafkaSchemaHistory Configuration Kafka Connect	2	868	17 March 2025
How to make connector using pre-defined schema on topic Kafka Connect	0	3005	10 December 2021
Debezium schema Kafka Connect	2	2619	18 May 2023
My debezium do not create the schema change topic on confluent cloud Confluent Cloud	0	1906	28 August 2023
Debezium Oracle kafka connector Kafka Connect	3	638	25 July 2024

Debezium Connector: Filtering Specific Tables and Preventing Schema History for All Tables

Related topics