the current conflict validation (implemented in https://jira.mongodb.org/browse/SERVER-121977 ) will return a write conflict on any change between planScan and commitFiles in our iceberg write flow. however, if a change happened in a partition that's different from the ones we want to write to, then there's not really a conflict there. we can add smarter conflict validation by passing an expression filter into the RowDelta- i've drafted the change here but it needs some TLC: https://github.com/10gen/mongo/pull/50114