[Spark]Add VacuumProtocolCheck ReaderWriter Table Feature #2730
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sumeet-db
force-pushed
the
vacuum-changes-1
branch
2 times, most recently
from
d20d65f to
d189748
Compare
prakharjain09
approved these changes
Mar 12, 2024
sumeet-db
force-pushed
the
vacuum-changes-1
branch
from
d189748 to
0f53f11
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Add a new VacuumProtocolCheck ReaderWriter Table Feature so that Vacuum command on older DBR client and OSS clients fail.
This is in follow-up to #2557 where protocol-check was added during the vacuum-write flow.
How was this patch tested?
UTs
Does this PR introduce any user-facing changes?
No