[ 
https://issues.apache.org/jira/browse/IMPALA-15083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnab Karmakar updated IMPALA-15083:
------------------------------------
    Description: 
Iceberg's UUID type is stored as {{{{{}FIXED_LEN_BYTE_ARRAY(16)}}{}}} in 
Parquet with a UUID logical type annotation. Currently Impala throws 
`{{{}"Iceberg type 'UUID' is not supported in Impala"`{}}} in 
`{{{}IcebergSchemaConverter.toImpalaType()`{}}}.

Add read support by exposing UUID values as STRING in canonical RFC 4122 format 
(`{{{}xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`{}}}).

  was:
Iceberg's UUID type is stored as `{{{}FIXED_LEN_BYTE_ARRAY(16)`{}}} in Parquet 
with a UUID logical type annotation. Currently Impala throws `{{{}"Iceberg type 
'UUID' is not supported in Impala"`{}}} in 
`{{{}IcebergSchemaConverter.toImpalaType()`{}}}.

Add read support by exposing UUID values as STRING in canonical RFC 4122 format 
(`{{{}xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`{}}}).


> Add Iceberg UUID data type read support
> ---------------------------------------
>
>                 Key: IMPALA-15083
>                 URL: https://issues.apache.org/jira/browse/IMPALA-15083
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend, Frontend
>            Reporter: Arnab Karmakar
>            Assignee: Arnab Karmakar
>            Priority: Major
>              Labels: impala-iceberg
>
> Iceberg's UUID type is stored as {{{{{}FIXED_LEN_BYTE_ARRAY(16)}}{}}} in 
> Parquet with a UUID logical type annotation. Currently Impala throws 
> `{{{}"Iceberg type 'UUID' is not supported in Impala"`{}}} in 
> `{{{}IcebergSchemaConverter.toImpalaType()`{}}}.
> Add read support by exposing UUID values as STRING in canonical RFC 4122 
> format (`{{{}xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`{}}}).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to