-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
None
-
False
-
0
-
0%
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
Debezium synchronizes data with SQL Server DB by enabling the CDC function in the tables of SQL Server. Multiple "capture_instance" can be created, and each capture_instance can specify different fields. The debezium connector seems to have no parameters to specify capture_instance.
For example, the "dbo. TEST 01" table in the SQL server database has three fields (id, name, age). To enable the CDC function for this table, create a "capture_instance" named custom1 and capture the fields (id, name, age). Debezium will store the structure of this table in the "history topic" of Kafka. Create another "capture_instance" named custom2, capture the field as (id), and debezium will update the table structure of this table in Kafka. If debezium has specified the "capture_instance" parameter configuration, can the table structure not be updated.
This is the result I want
Configuration parameters for SQL Server DB:
Debezium's explanation for table updates :
https://debezium.io/documentation/reference/2.5/connectors/sqlserver.html#sqlserver-schema-evolution
What Debezium connector do you use and what version?
I am using Debezium Sqlserver Source connector, and the version is 2.3.0.
What is the connector configuration?
{
"name": "sqlserver-connector-94",
"config":
}
What is the captured database version and mode of depoyment?
SQLServer
Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64) Oct 8 2022 05:58:25 Copyright (C) 2022 Microsoft Corporation Developer Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)
KAFKA Version: 2.12-2.4.1
What behaviour do you expect?
I expect Debezium to have the ability to specify the "capture_instance" parameter configuration, so that when I create multiple "capture_instances" in SQL Server, Debezium will not update the table structure
What behaviour do you see?
<Your answer>
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Haven't seen
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
This is not an error .
How to reproduce the issue using our tutorial deployment?
<Your answer>
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Debezium synchronizes data with SQL Server DB by enabling the CDC function in the tables of SQL Server. Multiple "capture_instance" can be created, and each capture_instance can specify different fields. The debezium connector seems to have no parameters to specify capture_instance.
For example, the "dbo. TEST 01" table in the SQL server database has three fields (id, name, age). To enable the CDC function for this table, create a "capture_instance" named custom1 and capture the fields (id, name, age). Debezium will store the structure of this table in the "history topic" of Kafka. Create another "capture_instance" named custom2, capture the field as (id), and debezium will update the table structure of this table in Kafka. If debezium has specified the "capture_instance" parameter configuration, can the table structure not be updated.
This is the result I want
Which use case/requirement will be addressed by the proposed feature?
<Your answer>
Implementation ideas (optional)
Not currently available