fix(table): skip RemoveSnapshotsUpdate when no snapshots to expire #679
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ExpireSnapshots was adding a RemoveSnapshotsUpdate even when there were no snapshots to delete. This caused Commit to create a new metadata file on every call, even when nothing changed, leading to metadata file proliferation in maintenance jobs that leverage iceberg-go's snapshot expiration implementation.