Resolving concurrent write conflicts for Apache Iceberg tables in Amazon Redshift
Big Data Blog
Amazon Redshift now automatically resolves concurrent write conflicts for Apache Iceberg tables by rebasing non-overlapping changes instead of aborting them.
- Escalates conflict checks from operation-level to partition-level to file-level granularity
- Resolves any write alongside concurrent appends, and row-level writes to different partitions or files
- Eliminates need to serialize writers, partition tables, or implement application-side retry loops
- Improves write throughput by up to 12x at 16 concurrent writers with no rejected commits
- Reduced concurrent-write conflict errors to nearly zero after fleet deployment in September 2026
- Available on patch 203 or later with no configuration required
Automatic conflict resolution enables production data lakes to handle concurrent writes safely while maintaining snapshot isolation semantics and data correctness.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Apr 8
2025
2025
Manage concurrent write conflicts in Apache Iceberg on the AWS Glue Data Catalog
Nov 13
2026
2026
Multi-statement transactions for Apache Iceberg tables in Amazon Redshift
Sep 28
2026
2026
Getting started with Apache Iceberg write support in Amazon Redshift – Part 3
Nov 17
2025
2025
Amazon Redshift now supports writing to Apache Iceberg tables
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.