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

Raghav Jindal reassigned IMPALA-12536:
--------------------------------------

    Assignee: Raghav Jindal

> Impala cannot read Iceberg tables with TIMESTAMPTZ if the data file format is 
> Avro
> ----------------------------------------------------------------------------------
>
>                 Key: IMPALA-12536
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12536
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend, Frontend
>            Reporter: Zoltán Borók-Nagy
>            Assignee: Raghav Jindal
>            Priority: Major
>              Labels: impala-iceberg
>
> Tables are created via Spark:
> {noformat}
>         sql(s"""
>         CREATE TABLE $tableName (
>           id INT,
>           date DATE,
>           timestamp TIMESTAMP)
>           USING iceberg
>           TBLPROPERTIES('${TableProperties.DEFAULT_FILE_FORMAT}' = 
> '$fileFormat')"""){noformat}
> Impala is able to read the table if the file format is Parquet or ORC, but 
> when the file format is Avro, it throws the following exception:
> {noformat}
> ERROR: AnalysisException: Failed to load metadata for table: 
> 'date_timestamp_table_avro'
> CAUSED BY: TableLoadingException: Could not load table 
> spark_iceberg.date_timestamp_table_avro from catalog
> CAUSED BY: TException: 
> TGetPartialCatalogObjectResponse(status:TStatus(status_code:GENERAL, 
> error_msgs:[IcebergTableLoadingException: Error loading metadata for Iceberg 
> table 
> hdfs://.../warehouse/tablespace/external/hive/spark_iceberg.db/date_timestamp_table_avro
> CAUSED BY: UnsupportedOperationException: timestamp with local time zone is 
> not a suppported Impala type]), lookup_status:OK){noformat}



--
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