Spark 3.3/3.4: support read of partition metadata column when table is over 1k#10641
Merged
szehon-ho merged 2 commits intoJul 12, 2024
Merged
Conversation
…s over 1k Backport of PR#10547
Contributor
Author
|
@szehon-ho or @RussellSpitzer if you want to take a look at this back port |
Contributor
Author
szehon-ho
approved these changes
Jul 12, 2024
Member
|
Merged, thanks @dramaticlly |
jasonf20
pushed a commit
to jasonf20/iceberg
that referenced
this pull request
Aug 4, 2024
zachdisc
pushed a commit
to zachdisc/iceberg
that referenced
this pull request
Dec 23, 2024
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
2 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.
Backport of pull request #10547 but looks like junit5 and assertJ is not there so keep the original unit test style. Also skip the vectorized read of ORC in Spark 3.3 unit tests