[jira] [Commented] (FLINK-34903) Add mysql-pipeline-connector with table.exclude.list option to exclude unnecessary tables
[ https://issues.apache.org/jira/browse/FLINK-34903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829718#comment-17829718 ] Thorne commented on FLINK-34903: ok,tks,i have do it > Add mysql-pipeline-connector with table.exclude.list option to exclude > unnecessary tables > --- > > Key: FLINK-34903 > URL: https://issues.apache.org/jira/browse/FLINK-34903 > Project: Flink > Issue Type: Improvement > Components: Flink CDC >Reporter: Thorne >Priority: Major > Labels: cdc > Fix For: cdc-3.1.0 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > Original Estimate: 72h > Remaining Estimate: 72h > > When using the MySQL Pipeline connector for whole-database > synchronization, users currently cannot exclude unnecessary tables. Taking > reference from Debezium's parameters, specifically the > {*}table.exclude.list{*}, if the *table.include.list* is declared, then the > *table.exclude.list* parameter will not take effect. However, the tables > specified in the tables parameter of the MySQL Pipeline connector are > effectively added to the *table.include.list* in Debezium's context. > !screenshot-1.png! > !screenshot-2.png|width=834,height=86! > debezium opthion desc > !screenshot-3.png|width=831,height=217! > In summary, it is necessary to introduce an externally-exposed > *table.exclude.list* parameter within the MySQL Pipeline connector to > facilitate the exclusion of tables. This is because the current setup does > not allow for excluding unnecessary tables when including others through the > tables parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34903) Add mysql-pipeline-connector with table.exclude.list option to exclude unnecessary tables
[ https://issues.apache.org/jira/browse/FLINK-34903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829715#comment-17829715 ] Hongshun Wang commented on FLINK-34903: --- [~fffy] , Please change PR titile by [FLINK-34903][]Add mysql-pipeline-connector with table.exclude.list option to exclude unnecessary tables > Add mysql-pipeline-connector with table.exclude.list option to exclude > unnecessary tables > --- > > Key: FLINK-34903 > URL: https://issues.apache.org/jira/browse/FLINK-34903 > Project: Flink > Issue Type: Improvement > Components: Flink CDC >Reporter: Thorne >Priority: Major > Labels: cdc > Fix For: cdc-3.1.0 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > Original Estimate: 72h > Remaining Estimate: 72h > > When using the MySQL Pipeline connector for whole-database > synchronization, users currently cannot exclude unnecessary tables. Taking > reference from Debezium's parameters, specifically the > {*}table.exclude.list{*}, if the *table.include.list* is declared, then the > *table.exclude.list* parameter will not take effect. However, the tables > specified in the tables parameter of the MySQL Pipeline connector are > effectively added to the *table.include.list* in Debezium's context. > !screenshot-1.png! > !screenshot-2.png|width=834,height=86! > debezium opthion desc > !screenshot-3.png|width=831,height=217! > In summary, it is necessary to introduce an externally-exposed > *table.exclude.list* parameter within the MySQL Pipeline connector to > facilitate the exclusion of tables. This is because the current setup does > not allow for excluding unnecessary tables when including others through the > tables parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34903) Add mysql-pipeline-connector with table.exclude.list option to exclude unnecessary tables
[ https://issues.apache.org/jira/browse/FLINK-34903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829512#comment-17829512 ] Thorne commented on FLINK-34903: i take a pr in https://github.com/apache/flink-cdc/pull/3186 > Add mysql-pipeline-connector with table.exclude.list option to exclude > unnecessary tables > --- > > Key: FLINK-34903 > URL: https://issues.apache.org/jira/browse/FLINK-34903 > Project: Flink > Issue Type: Improvement > Components: Flink CDC >Reporter: Thorne >Priority: Major > Labels: cdc > Fix For: cdc-3.1.0 > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > Original Estimate: 72h > Remaining Estimate: 72h > > When using the MySQL Pipeline connector for whole-database > synchronization, users currently cannot exclude unnecessary tables. Taking > reference from Debezium's parameters, specifically the > {*}table.exclude.list{*}, if the *table.include.list* is declared, then the > *table.exclude.list* parameter will not take effect. However, the tables > specified in the tables parameter of the MySQL Pipeline connector are > effectively added to the *table.include.list* in Debezium's context. > In summary, it is necessary to introduce an externally-exposed > *table.exclude.list* parameter within the MySQL Pipeline connector to > facilitate the exclusion of tables. This is because the current setup does > not allow for excluding unnecessary tables when including others through the > tables parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FLINK-34903) Add mysql-pipeline-connector with table.exclude.list option to exclude unnecessary tables
[ https://issues.apache.org/jira/browse/FLINK-34903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829418#comment-17829418 ] Thorne commented on FLINK-34903: I will take a pr for this > Add mysql-pipeline-connector with table.exclude.list option to exclude > unnecessary tables > --- > > Key: FLINK-34903 > URL: https://issues.apache.org/jira/browse/FLINK-34903 > Project: Flink > Issue Type: Improvement > Components: Flink CDC >Reporter: Thorne >Priority: Major > Labels: cdc > Fix For: cdc-3.1.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > When using the MySQL Pipeline connector for whole-database > synchronization, users currently cannot exclude unnecessary tables. Taking > reference from Debezium's parameters, specifically the > {*}table.exclude.list{*}, if the *table.include.list* is declared, then the > *table.exclude.list* parameter will not take effect. However, the tables > specified in the tables parameter of the MySQL Pipeline connector are > effectively added to the *table.include.list* in Debezium's context. > In summary, it is necessary to introduce an externally-exposed > *table.exclude.list* parameter within the MySQL Pipeline connector to > facilitate the exclusion of tables. This is because the current setup does > not allow for excluding unnecessary tables when including others through the > tables parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)