Spark 3.3: Remove unnecessary metadata columns reading when merge using Iceberg table #7985
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
Contributor
Author
|
Hi @rdblue @szehon-ho @aokolnychyi @RussellSpitzer @Fokko, could you please help to review this when you are free? Thanks a lot. |
Member
|
@huaxingao I believe you did the Spark fix for this? |
Contributor
|
I think the problem has already been fixed in Spark 3.3 by this PR |
Contributor
Author
|
Thanks @RussellSpitzer @huaxingao, I see, that's because the Spark 3.3.3 is not released. |
Contributor
Author
|
Close this since Spark 3.3 has been fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
There are many unnecessary metadata columns reading when merging using the Iceberg table. The problem should be caused by Spark 3.3 AddMetadataColumns rule which has been fixed in Spark 3.4.
In this PR, we add a rule to remove the unnecessary metadata column reading to fix the problem in Spark 3.3.
Before this PR:
After this PR:
