icchux opened a new issue, #238: URL: https://github.com/apache/doris-flink-connector/issues/238
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-doris/issues?q=is%3Aissue) and found no similar issues. ### Version master branch ``` <revision>1.5.0-SNAPSHOT</revision> <flink.version>1.16.0</flink.version> <flink.minor.version>1.16</flink.minor.version> <flink.sql.cdc.version>2.4.1</flink.sql.cdc.version> ``` ### What's Wrong? mysql-sync-database -use-new-schema-change when the program starts for the first time, firstSchemeChange==true will initialize the originFieldSchema Map, but the number of fields in updateFiledSchema is the same as that in originFieldSchema Map, no subsequent ddl changes will be made. [the main method follow](https://github.com/apache/doris-flink-connector/blob/master/flink-doris-connector/src/main/java/org/apache/doris/flink/sink/writer/serializer/JsonDebeziumSchemaSerializer.java#L238) ### What You Expected? expected it do correct at the first schema change after job start ### How to Reproduce? and Here are my execution steps： 1. ```alter table test3 add state_10 tinyint null comment '状态'; ``` sync schema change failed : INFO org.apache.doris.flink.sink.writer.JsonDebeziumSchemaSerializer [Source: MySQL Source -> Process -> test3: Writer -> test3: Committer (1/10)#0] - ddl can not do schema change: *** 2. ``` alter table test3 add state_11 tinyint null comment '状态' ``` sync schema change success : INFO org.apache.doris.flink.sink.writer.JsonDebeziumSchemaSerializer [Source: MySQL Source -> Process -> test3: Writer -> test3: Committer (1/10)#0] - schema change status:true, ddl:ALTER TABLE test.test3 ADD COLUMN state_11 TINYINT ### Anything Else? _No response_ ### Are you willing to submit PR? - [ ] 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
