thesumery opened a new issue, #6401: URL: https://github.com/apache/inlong/issues/6401
### What happened Schema update stuck in dead loop cause stackoverflow in multiple sink scences  ### What you expected to happen Schema update success or fail in multiple sink scences. ### How to reproduce 1. prepare a mysql 5.7+ and flink 1.13 and iceberg env 2. create a mysql table and insert some data ``` use inlong; create table if not exists `inlong_input13` ( `id` bigint, `name` varchar(63), PRIMARY KEY(id) ); insert into inlong_input13 (id, name) values (1, 'haha'); insert into inlong_input13 (id, name) values (2, 'xixi'); ``` 3. create a sort link in flink client ``` CREATE TABLE `table_1`( `data` STRING METADATA FROM 'meta.data' VIRTUAL) WITH ( 'migrate-all' = 'true', 'connector' = 'mysql-cdc-inlong', 'hostname' = 'localhost', 'database-name' = 'inlong', -- 如果要匹配所有的则使用正则匹配 'scan.incremental.snapshot.enabled' = 'false', 'username' = 'root', 'password' = '123456', 'table-name' = '[\s\S]*.*' ); CREATE TABLE `table_2`( `data` STRING) WITH ( 'connector'='iceberg-inlong', 'catalog-name'='hive_prod', 'uri'='thrift://localhost:9083', 'warehouse'='hdfs://localhost:8020/hive/warehouse', 'sink.multiple.enable' = 'true', 'sink.multiple.format' = 'canal-json', 'sink.multiple.add-column.policy' = 'TRY_IT_BEST', 'sink.multiple.database-pattern' = '${database}', 'sink.multiple.table-pattern' = 'test_${table}' ); insert into table_2 select `data` as `data` from table_1; ``` 4. modify myslq table one column name ``` ALTER TABLE inlong_input13 RENAME name to name1; insert into inlong_input13 (id, name1) values (3, 'OOO'); ``` ### Environment _No response_ ### InLong version master ### InLong Component InLong Sort ### Are you willing to submit PR? - [X] Yes, I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
