Repository navigation
Spark 4.1: Use table IDs in scan equals/hashCode - #15363
Merged
Merged
Conversation
singhpk234
reviewed
Feb 19, 2026
singhpk234
left a comment
singhpk234
left a comment
Contributor
There was a problem hiding this comment.
LGTM, since we already have name()
optional : may be a test would nice :)
singhpk234
approved these changes
Feb 19, 2026
Contributor
Author
|
@singhpk234, seems like there is no existing test suite, I will add one in #15240. |
Contributor
Author
|
Thanks, @singhpk234! |
RjLi13
pushed a commit
to RjLi13/iceberg
that referenced
this pull request
Mar 12, 2026
talatuyarer
pushed a commit
to talatuyarer/iceberg
that referenced
this pull request
Apr 1, 2026
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.
This PR adds table IDs to scan equals/hashCode implementations.