Problemsby IbisApache Flink schema changes break downstream pipelines
Data engineering2 posts from 2 people2d active+00 posts in the last 7 days, 1 the 7 days before (fading)Unverified
Posts per day
The posts behind it
2, newest firstFlink: DynamicIcebergSink TableMetadataCache matches historical schemas by name, causing writes with retired field ids**Apache Iceberg version:** 1.12.0 (reproduced). The code involved appears unchanged on `main` (`flink/v2.3`), so the same behaviour is expected there. **Query engine:** Flink (`DynamicIcebergSink`, DataStream API, upsert mode) **Please describe the bug 🐞** ### Summary...apache/iceberg · kuni-922 repliesOpen ↗Flink: DynamicIcebergSink still duplicates a row when a key column's optionality, type or order, or the equality-field set, changes within one checkpoint**Apache Iceberg version:** `main` (`flink/v2.3`) with the fix proposed for #18262 in #18288. On released versions, including 1.11.0, these cases already duplicate as part of #18262. **Query engine:** Flink (`DynamicIcebergSink`, upsert and CDC modes) **Please describe the bug...apache/iceberg · abrarsher231 repliesOpen ↗
Companies and products named
About this problem
Evidence
2 posts from 2 people in 1 place, about 1 a week over 13 days. Mostly on apache/iceberg. Tools named alongside: Apache Iceberg.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "schema-drift" rule about Apache Flink. First post Oct 2, 2026, latest Oct 14, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
Other Apache Flink problems
History
steady to fading
Apache Flink schema changes break downstream pipelines (2 posts)