Enhance: RewriteAction conflict detection and resolution

[Li0k]

Backgroud

During the compaction process, the iceberg table may have added a new snapshot, and the submission will cause a conflict.

1. Other snapshots (non-replace) have been written during the compaction period, so the compaction result has no actual conflict with the latest snapshot and can be reapplied

2. Other replace operations have been written during the compaction period, and the compaction input no longer exists. At this time, it is necessary to detect the conflict and abandon the compaction result to avoid data errors.

Solution

1. For situation 1, add a retry operation to commit. When the transaction fails to commit, re-obtain the latest table snapshot and re-execute the action apply.

2. For situation 2

• SDK prohibits the removal of non-existent files.

• Add conflict detection before committing to reduce commit counts.

[Li0k]

@chenzl25 @xxhZs

any suggestion?

[Li0k]

According to the current plan, I will implement retry-based conflict resolution first.

[xxhZs]

According to the current plan, I will implement retry-based conflict resolution first.

+1