zhangkunjie created FLINK-35807:
-----------------------------------
Summary: When restoring a task from a savepoint, tables that were
previously synchronized but later deleted still exist in a state
Key: FLINK-35807
URL: https://issues.apache.org/jira/browse/FLINK-35807
Project: Flink
Issue Type: Bug
Components: Flink CDC
Affects Versions: cdc-3.1.1
Environment: Mysql5.7+Flink1.18.1+Flink CDC 3.1.1
Reporter: zhangkunjie
1、I configured MySQL tables A and B to synchronize to a pipeline in Starrocks
using the configuration file yaml Task.
2、I use the flink savepoint command to save the running task as a _metadata.
3、I modified the yaml configuration file by commenting out Table B, leaving
only Table A, and then restoring the task from the second step's savepoint. At
this point, the synchronization task only synchronizes Table A, which is not a
problem.
4、At this point, I used the flink savepoint command again to save the running
task as a _metadata. Through observation, it was found that the information of
Table B, which had already been deleted, still exists in the _metadata at this
time. Why does the deleted B table information still exist in the _metadata?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
