Spark 3.5, Core: Supplement test case for metadata_log_entries after expire snapshot #11901
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
…expire snapshot And fix some incorrectness in the code comments.
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.
When we query
metadata_log_entriesafter expiring some intermediate snapshots, the log entries before the expired snapshot would not get their corresponding snapshots and then would shownullin their result columnslatest_snapshot_id,latest_schema_idandlatest_sequence_number.This PR supplement test case for this scenario to increase test coverage.
And fix some incorrectness in the code comments in
TableMetadataandMetadataLogEntriesTable.