Spark 3.4: Backport UPDATE/MERGE logic for row lineage #13344
+975
−17
Conversation
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 PR back ports the row lineage support in row-level operations from Spark 3.5 that was done in #12736 to Spark 3.4. Which was mostly a 1:1 port from 3.5, however Spark 3.4 uses custom Iceberg rules that aren't exactly the same as the changes that were merged into Spark itself.
Key Differences from 3.5
MergeIntoIcebergTable, UpdateIcebergTable) So we adapt to use these insteadWHEN NOT MATCHED BY SOURCE, so we ingore in backportSparkParquetReaderdidn't have handling for row lineage columns yetEverything else was a straight port from 3.5 with the logical plan name changes.
cc: @amogh-jahagirdar