# Resolving concurrent write conflicts for Apache Iceberg tables in Amazon Redshift

DevFeed: [Resolving concurrent write conflicts for Apache Iceberg tables in Amazon Redshift](<https://devfeed.tech/articles/resolving-concurrent-write-conflicts-for-apache-iceberg-tables-in-amazon-redshift-86417.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/resolving-concurrent-write-conflicts-for-apache-iceberg-tables-in-amazon-redshift/>)

Author: Sanjay Devireddy

Published: 2026-10-13T20:16:48Z

Content type: article

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [Amazon S3 Tables](<https://devfeed.tech/topics/amazon-s3-tables.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>)

Tags: [amazon-redshift](<https://devfeed.tech/tags/amazon-redshift.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-iceberg-tables](<https://devfeed.tech/tags/apache-iceberg-tables.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [concurrency-control](<https://devfeed.tech/tags/concurrency-control.md>), [conflict-resolution](<https://devfeed.tech/tags/conflict-resolution.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>)

## AI overview

Amazon Redshift now automatically rebases many concurrent writes to Apache Iceberg tables when metadata shows that the changes do not overlap. The article explains how Redshift checks conflicts at operation, partition, and file levels, and describes benchmark results for append-only writers. In the reported 16-writer test, automatic resolution completed 12 times more commits in the same period than basic optimistic concurrency mode, with no rejected commits in the measured configurations.

## Source excerpt

Amazon Redshift now automatically resolves many concurrent writes to Apache Iceberg tables that don't actually overlap, committing changes that previously failed and had to retry. Learn why these writes conflict, how the engine rebases non-overlapping ones across operation, partition, and file checks, and the throughput gains it delivers.