Schema compatibility functions - #2073
Open
rambleraptor wants to merge 2 commits into
Open
rambleraptor wants to merge 2 commits into
rambleraptor wants to merge 2 commits into
Conversation
rambleraptor
marked this pull request as ready for review
September 29, 2026 21:17
This branch has not been deployed
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
1 participant
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 adds schema compatibility checks (which relates to Java's CheckCompatibility). This is wildly useful for ensuring that schemas are allowed according to the Iceberg spec. Terraform uses this functionality extensively...and we've implemented a good bit of it ourselves, which I'd like to get out of the habit of.
AI Disclosure: Claude built this for me under my supervision. I noticed that this was one of a few places where we could take Terraform functionality and upstream it for everyone.