emkornfield commented on code in PR #10831:
URL: https://github.com/apache/iceberg/pull/10831#discussion_r1858978402


##########
format/spec.md:
##########
@@ -182,6 +182,21 @@ A **`list`** is a collection of values with some element 
type. The element field
 
 A **`map`** is a collection of key-value pairs with a key type and a value 
type. Both the key field and value field each have an integer id that is unique 
in the table schema. Map keys are required and map values can be either 
optional or required. Both map keys and map values may be any type, including 
nested types.
 
+#### Semi-structured Types
+
+A **`variant`** is a value that stores semi-structured data. The structure and 
data types in a variant are not necessarily consistent across rows in a table 
or data file. The variant type and binary encoding are defined in the [Parquet 
project](https://github.com/apache/parquet-format/blob/4f208158dba80ff4bff4afaa4441d7270103dff6/VariantEncoding.md).
 Support for Variant is added in Iceberg v3.
+
+Variants are similar to JSON with a wider set of primitive values including 
date, timestamp, timestamptz, binary, and floating points.
+
+Variant values may contain nested types:
+1. An array is an ordered collection of variant values.
+2. An object is a collection of fields that are a string key and a variant 
value.
+
+As a semi-structured type, there are important differences between variant and 
Iceberg's other types:
+1. Variant arrays are similar to lists, but may contain any variant value 
rather than a fixed element type.
+2. Variant objects are similar to structs, but may contain variable fields 
identified by name and field values may be any variant value rather than a 
fixed field type.
+3. Variant primitives are narrower than Iceberg's primitive types: time, 
timestamp_ns, timestamptz_ns, uuid, and fixed(L) are not supported.

Review Comment:
   I imagine the parquet changes to the variant spec would be merged before we 
release v3?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org

Reply via email to