[iceberg] Support the variant type in Iceberg schema type conversion#8795
Open
plusplusjiajia wants to merge 1 commit into
Open
[iceberg] Support the variant type in Iceberg schema type conversion#8795plusplusjiajia wants to merge 1 commit into
plusplusjiajia wants to merge 1 commit into
Conversation
…mon Iceberg compatibility
plusplusjiajia
force-pushed
the
gh-iceberg-variant
branch
from
July 23, 2026 13:03
b3357d7 to
e1e82d9
Compare
plusplusjiajia
marked this pull request as ready for review
July 23, 2026 13:31
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.
Purpose
Map the Iceberg
varianttype inIcebergDataFieldso a schema with aVariantTypecolumn converts between Paimon and Iceberg types both ways; before this it threw
Unsupported data type: VariantType.variantis an Iceberg v3 type needing row lineage, which Paimon's own Iceberg metadatageneration does not support, so a schema containing it is rejected during metadata
generation (as an older release already did) rather than emitting unreadable metadata.
Also fixes a pre-existing bug: an array's
element-requiredflag was taken from thearray's nullability instead of the element type's.
Note
Rejection happens during post-commit metadata generation (a property of Paimon's
Iceberg callback, unchanged from the prior
Unsupported data typebehavior), not atwrite validation.
Tests
IcebergDataFieldTest: variant forward/reverse conversion, JSON round-trip, arrayelement-nullability.
IcebergCompatibilityTest: rejects a schema containing variant.RESTCatalogTest#testCreateIcebergTable: variant column round-trips through create + get.