[SPARK-59640][SDP] SCD2 Ignore-null support; add version-map authorship operations - #58914
Open
AnishMahto wants to merge 18 commits into
Open
AnishMahto wants to merge 18 commits into
AnishMahto wants to merge 18 commits into
Conversation
Contributor
Author
|
@jose-torres for review. Pretty short (if you don't include tests or scaladocs!) and well contained PR. Version map APIs added are not yet actually used during reconciliation, but are all unit tested. They will be used in the next PR in the stack, which I will put up soon. |
This file contains hidden or 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
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.
This is a stacked PR. See incremental diff here: AnishMahto/spark@SPARK-59183-populate-verison-map-at-ingest...SPARK-59640-scd2-version-map-authorship-operations.
See previous PR in stack here: #58645
What changes were proposed in this pull request?
Implement the operations that SCD2 ignore-null coalescing will need to use to interface with the version map to determine leaf authorship, lazy materialization on schema evolution, etc.
Why are the changes needed?
Interfaces needed for SCD2 ignore null coalescing (future PRs) to determine and update authorship information in a row's version map.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit tests added to
Scd2VersionMapSuite.Was this patch authored or co-authored using generative AI tooling?
Co-authored with GPT Sol 5.6.