[jira] [Commented] (FLINK-34925) FlinkCDC 3.0 for extracting data from sqlserver, errors occur
[ https://issues.apache.org/jira/browse/FLINK-34925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830794#comment-17830794 ] 宇宙先生 commented on FLINK-34925: -- [~loserwang1024] Maybe,I dont konw how to resolve it, and why.if u have any views ,pls contact me. thanks a a lot. > 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)
[jira] [Commented] (FLINK-34925) FlinkCDC 3.0 for extracting data from sqlserver, errors occur
[ https://issues.apache.org/jira/browse/FLINK-34925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830759#comment-17830759 ] Hongshun Wang commented on FLINK-34925: --- [~gongzhongqiang] , CC, I am not familiar with Sqlserver. Whether is it an index format that Debezium cannot parse. > 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)
[jira] [Commented] (FLINK-34925) FlinkCDC 3.0 for extracting data from sqlserver, errors occur
[ https://issues.apache.org/jira/browse/FLINK-34925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830750#comment-17830750 ] 宇宙先生 commented on FLINK-34925: -- thanks for ur replay again. my table DDL sql is SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [dbo].[history]( [id] [dbo].[dtMMM_TableID] IDENTITY(1,1) NOT NULL, [mmm_code_id] [int] NULL, [reference_no] [nvarchar](255) NOT NULL, [img_url] [text] NULL, [quantity] [float] NOT NULL, [handover_from] [nvarchar](255) NOT NULL, [handover_to] [nvarchar](255) NOT NULL, [handover_time] [datetime] NOT NULL, [return_type] [nvarchar](50) NULL, [PhysicalCheck] [bit] NULL, [reference_type] [varchar](32) NULL, [sign_off_no] [varchar](32) NULL, [part_no] [varchar](64) NULL, [serial_no] [varchar](64) NULL, [remark] [varchar](250) NULL, [version] [int] NULL, [exception] [varchar](500) NULL, [update_time] [datetime] NULL, [update_by] [varchar](16) NULL, CONSTRAINT [PK_history] PRIMARY KEY CLUSTERED ( [id] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY] GO > 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)
[jira] [Commented] (FLINK-34925) FlinkCDC 3.0 for extracting data from sqlserver, errors occur
[ https://issues.apache.org/jira/browse/FLINK-34925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830464#comment-17830464 ] Hongshun Wang commented on FLINK-34925: --- This [DBZ-5398|https://issues.redhat.com/browse/DBZ-5398] is for PG Table with functional index, maybe same problem with sqlserver? What's your table DDL? > 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)
[jira] [Commented] (FLINK-34925) FlinkCDC 3.0 for extracting data from sqlserver, errors occur
[ https://issues.apache.org/jira/browse/FLINK-34925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830356#comment-17830356 ] 宇宙先生 commented on FLINK-34925: -- [~loserwang1024] thanks for ur replay, may I have your details about the problem, process stps and so on.,Thanks again. > 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)
[jira] [Commented] (FLINK-34925) FlinkCDC 3.0 for extracting data from sqlserver, errors occur
[ https://issues.apache.org/jira/browse/FLINK-34925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
