HIVE-29699: Iceberg: Add support for the Unknown data type#6588
Draft
difin wants to merge 1 commit into
Draft
Conversation
difin
force-pushed
the
unknown_data_type
branch
2 times, most recently
from
730ddb2 to
0267596
Compare
asf-ci-hive
added
tests pending
tests unstable
and removed
tests unstable
tests pending
labels
|
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.
What changes were proposed in this pull request?
This PR adds Iceberg V3 UNKNOWN type support in Hive, following the same pattern as VARIANT: new serde/types, parser token, schema conversion, object inspectors, and wiring through DDL, semantic analysis, and vectorized execution.
Why are the changes needed?
Iceberg format version 3 introduced the unknown type for placeholder columns that only accept NULL. Hive needs explicit support for that type in its parser, serde, schema conversion, and execution paths, or Iceberg V3 tables using unknown fail on create, insert, select, and alter.
Does this PR introduce any user-facing change?
Yes.
Users can define and use the UNKNOWN type on Iceberg tables: create columns, insert NULL, select, and add columns via ALTER TABLE.
How was this patch tested?
Unit tests:
TestHiveStorageHandlerColumnTypesfor storage-handler column-type checks.Q-tests: positive
unknown_type.q(create, insert, select, alter, desc on v3);negative:
unknown_type_non_iceberg_table.qtests that UNKNOWN type cannot be used on native Hive tables.