Core: Fix metadata table scans when snapshot is null #3812
Merged
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.
This PR fixes an issue when scanning the snapshots (and history) metadata tables. When the current snapshot for a table is not set, then no snapshots will be returned during the scan. A table can get in this state if it has snapshots, then a
REPLACE TABLE
operation is performed. In this case, the snapshots are still present but will not be returned because the current snapshot is not set. If some data is committed to the table, and the current snapshot is set to something, then the previous snapshots that were not returned will show up again.Here is an example on how to reproduce with Spark SQL: