[Delta] Keep table protocol intact before and after REPLACE regardless of default CC enablement #4782
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.
Which Delta project/connector is this regarding?
Description
This PR keeps table protocol intact before and after REPLACE commands.
Under the current implementation, we have the following scenario that may automatically/silently upgrade a normal delta table's Protocol when using REPLACE commands. It would be upgraded from
(x, x)
(i.e., any combinations of protocol versions) to(3, 7)
, plus an additional (unintended)VacuumProtocolCheckTableFeature
.How was this patch tested?
N/A
Does this PR introduce any user-facing changes?
N/A