[
https://issues.apache.org/jira/browse/IMPALA-12404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761064#comment-17761064
]
Andrew Sherman commented on IMPALA-12404:
-----------------------------------------
I see we allow
{code:java}
create table ice_ts_part (i int, j timestamp)
partitioned by spec (j)
stored as iceberg;
{code}
and that shows this jira, but what does it mean to be partitioned by timestamp?
Won't each timestamp be different?
Maybe only partitioning of the form
{code:java}
create table ice_ts_part2 (i int, j timestamp)
partitioned by spec (day(j))
stored as iceberg
{code}
is useful.
> Insert fails on timestamp-partitioned Iceberg table
> ---------------------------------------------------
>
> Key: IMPALA-12404
> URL: https://issues.apache.org/jira/browse/IMPALA-12404
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 4.2.0
> Reporter: Peter Rozsa
> Priority: Major
> Labels: impala-iceberg
>
> Impala can't insert into Iceberg tables where partitioning contains a
> timestamp column.
> Insert statement fails with the following error:
> {code:java}
> ERROR: UnsupportedOperationException: Unsupported type for
> fromPartitionString: timestamp {code}
> The exception is thrown in the Iceberg API, when catalog tries to load the
> partition data from a datafile: org/apache/impala/util/IcebergUtil.java:715
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
