[Spark] Resolve inconsistencies between the V2 Checkpoint specification and implementation #2249
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
Follow-up for #2214.
The V2 Checkpoint implementation does not match with what is expected in the PROTOCOL in some places.
It does not write some fields in the V2 Checkpoint-related actions:
Also,
version
(checkpoint version) in checkpointMetadata and relies on it but the PROTOCOL does not specify any such fields.fileName
in the sidecar action. But the implementation writes this under the field namepath
.This PR updates the specification so that it correctly reflects the implementation.
Does this PR introduce any user-facing changes?
No