Nethaje commented on issue #9208: URL: https://github.com/apache/seatunnel/issues/9208#issuecomment-2854586825
Hi, I no longer encounter the update query issue after altering the schema, which I had reported earlier — it guess the problem might have been on my end. I'm currently running the job with the same configuration and same command-line arguments. However, I still do not see schema evolution working as expected. Here’s a summary of my observations: 1. Initial load from source to target using the CDC connector – Success 2. Updated the column device_id for a specific id (e.g., id=1) – Success 3. Altered the source table to add a new column test_column_1 with default value "test" – No schema change reflected in the target Iceberg table 4. Updated column device_id for another id (e.g., id=2) – The new column (test_column_1) appeared only for id=2; all other rows have null values 5. Inserted a new row in the source – test_column_1 value appears for the new row and id=2, but not for other existing rows 6. Renaming or deleting a column in the source – No changes reflected in the target Iceberg table Could you please confirm if this is the expected behavior, or if there's a resolution/workaround available for full schema evolution support? -- 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]
