pvary commented on issue #14425: URL: https://github.com/apache/iceberg/issues/14425#issuecomment-3489600884
> > Do I miss something? Is there something which could prevent us to use this method to prevent concurrent changes? > > The above test would fail for any concurrently added data file (because the default `conflictDetectionFilter()` is `true`). We only want to fail on duplicate data/delete files. There's no easy way to detect this using a conflict detection filter. That's why we need to use snapshot properties. So we could check the table state in case of a failure, and decide in the code how to move forward. We could refresh the table and check the last committed checkpoint before retrying again. > > This seems like a solution for a similar issue: [#14503](https://github.com/apache/iceberg/pull/14503) > > Yes, [#14445](https://github.com/apache/iceberg/pull/14445) can also work for Kafka Connect if we add validation methods to `PendingUpdate`. I suggest to participate in the review there so we have a generic solution for our problem too. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
