[
https://issues.apache.org/jira/browse/FLINK-34925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830310#comment-17830310
]
Hongshun Wang commented on FLINK-34925:
---------------------------------------
Debezium 2.0 is a major version upgrade which does not guarantee compatibility.
You can make some minor changes based on
[DBZ-5398|https://issues.redhat.com/browse/DBZ-5398] similar to what is done in
[https://github.com/apache/flink-cdc/pull/2842].
> FlinkCDC 3.0 for extracting data from sqlserver, errors occur
> ---------------------------------------------------------------
>
> Key: FLINK-34925
> URL: https://issues.apache.org/jira/browse/FLINK-34925
> Project: Flink
> Issue Type: Bug
> Components: Flink CDC
> Reporter: 宇宙先生
> Priority: Critical
> Attachments: image-2024-03-24-18-12-52-747.png,
> image-2024-03-24-18-23-19-657.png
>
>
> when I use FlinkCDC 3.0 for extracting data from sqlserver, errors occur
> !image-2024-03-24-18-12-52-747.png!
> .........is referenced as PRIMARY KEY, but a matching column is not defined
> in table.........
> I found some information on Debezuim's website，The official website says，
> This bug was fixed in the debe 2.0 version, I checked the current flinkcdc
> debezuim is version 1.97, I want to know what is the cause of this problem,
> can I directly upgrade the debezuim version to fix it? Debezuim's link
> [Debezium 2.0.0.Beta1
> Released|https://debezium.io/blog/2022/07/27/debezium-2.0-beta1-released/]
> !image-2024-03-24-18-23-19-657.png!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
