You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Hongshun Wang (Jira)" <ji...@apache.org> on 2024/08/25 08:34:00 UTC
[jira] [Created] (FLINK-36150) tables.exclude is not valid if scan.binlog.newly-added-table.enabled is true.
Hongshun Wang created FLINK-36150:
-------------------------------------
Summary: tables.exclude is not valid if scan.binlog.newly-added-table.enabled is true.
Key: FLINK-36150
URL: https://issues.apache.org/jira/browse/FLINK-36150
Project: Flink
Issue Type: Improvement
Components: Flink CDC
Affects Versions: cdc-3.1.1
Reporter: Hongshun Wang
Fix For: cdc-3.2.0
Current, `tables.exclude` is provided for user to exclude some table, because
tables passed to DataSource will be filtered when MySqlDataSourceFactory creates DataSource.
However, when scan.binlog.newly-added-table.enabled is true, new table ddl from binlog will be read and won't be filtered by `tables.exclude`.
This Jira aims to pass `tables.exclude` to MySqlSourceConfig and will use it when find tables from mysql database.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)