[ 
https://issues.apache.org/jira/browse/FLINK-34864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated FLINK-34864:
-----------------------------------
    Labels: github-import pull-request-available  (was: github-import)

> [enhancement] [ cdc-connector] [ignore no primary key table] When using 
> regular expressions to synchronize the entire database with Flink CDC, skip 
> tables that do not have a primary key.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-34864
>                 URL: https://issues.apache.org/jira/browse/FLINK-34864
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>            Reporter: Flink CDC Issue Import
>            Priority: Major
>              Labels: github-import, pull-request-available
>
> ### Search before asking
> - [x] I searched in the 
> [issues|https://github.com/ververica/flink-cdc-connectors/issues] and found 
> nothing similar.
> ### Motivation
> If regular expressions are used to match the tables to be synchronized, and 
> some tables in the database do not have a primary key, when submitting a task 
> with Flink CDC 3.0, an error occurs. Can we add an option to skip the 
> synchronization of tables without a primary key, such as 
> ignore-no-primary-key-table: true?
> **Flink version**
> 1.18
> **Flink CDC version**
> 3.0.0
> **Database and its version**
> Mysql 5.7 ,  StarRocks 3.2.2
> ### Solution
> ignore-no-primary-key-table: true
> ### Alternatives
> _No response_
> ### Anything else?
> _No response_
> ### Are you willing to submit a PR?
> - [ ] I'm willing to submit a PR!
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/apache/flink-cdc/issues/3006
> Created by: [everhopingandwaiting|https://github.com/everhopingandwaiting]
> Labels: enhancement, 
> Created at: Thu Jan 18 11:41:12 CST 2024
> State: open



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to