[
https://issues.apache.org/jira/browse/FLINK-36141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876218#comment-17876218
]
zhongyuandong edited comment on FLINK-36141 at 8/26/24 2:28 AM:
----------------------------------------------------------------
[~kunni] Is flink-cdc 3.3.0 only supported? We are using
flink-cdc-source-connectors 3.0.1, Switching to flinks-CDC-pipelin-connectors
was a pretty big adjustment for us, how can I use this feature? When will it be
used?
was (Author: JIRAUSER306741):
[~kunni] Is flink-cdc 3.4.0 only supported? We are using
flink-cdc-source-connectors 3.0.1, how can I use this feature? When will it be
used?
> [mysql]Set the scanNewlyAddedTableEnabled is true, but does not support
> automatic capture new added table
> ---------------------------------------------------------------------------------------------------------
>
> Key: FLINK-36141
> URL: https://issues.apache.org/jira/browse/FLINK-36141
> Project: Flink
> Issue Type: Bug
> Components: Flink CDC
> Affects Versions: cdc-3.1.0
> Reporter: zhongyuandong
> Priority: Critical
> Attachments: image-2024-08-23-11-07-26-384.png,
> image-2024-08-23-11-07-38-182.png, image-2024-08-23-11-08-31-324.png,
> image-2024-08-23-11-08-44-156.png
>
>
> 1、 see the flink-cdc3.0.1 debezium reader stage, specially added
> scanNewlyAddedTableEnabled is true filtered out, so lead to be inaccessible
> to the new table without restart? Based on 3.0.1 version design, testing the
> scanNewlyAddedTableEnabled = false (lost manually add table, restart
> operations cannot identify to), but it can automatically capture new added
> table with regular expressions without restarting them, is this a bug or
> purposely so design? (Why is it designed this way?)
> 2、 flink-cdc2.3.0 without this logic, can support the capture new added
> table. TODO: there is still very little chance that we can't capture new
> added table. Is this the reason why flink-cdc2.4.0 and later versions no
> longer support dynamic capture new added table?
> 3. Which version solves this problem? How to solve it?
> !image-2024-08-23-11-08-31-324.png!
> !image-2024-08-23-11-08-44-156.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
