# Issues with Quick Sight using Athena v3 and Iceberg timestamp columns **URL:** \ **Category:** Q&A\ **Tags:** data-ingestion, spice, data-source, s3, dataset, quick-sight\ **Created:** [January 26, 2023, 5:13pm UTC](https://community.amazonquick.com/t/issues-with-quick-sight-using-athena-v3-and-iceberg-timestamp-columns/9462 "2023-01-26T17:13:01Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Antonio\_Pintus](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/antonio_pintus/32/3160_2.png) [@Antonio\_Pintus](https://community.amazonquick.com/u/Antonio_Pintus)\ **Post date:** [January 26, 2023, 5:13pm UTC](https://community.amazonquick.com/t/issues-with-quick-sight-using-athena-v3-and-iceberg-timestamp-columns/9462/1 "2023-01-26T17:13:01Z")
Hi, I have an Iceberg Table with a column defined as of `timestamp` type. I’m experimenting with **Athena v3** Datasources in Quick Sight. Creating a Dataset from the Athena v3 Datasource, using a custom SQL to retrieve all columns, it works if the dataset is leaved in Direct Mode, and I’m able to build an analysis from that data, using the timestamp column as well. But, If I choose to change the Dataset to SPICE, then all rows are skipped due to a `MALFORMED_DATE` error for the timestamp column. In the Athena query editor I’m able to query the Iceberg table without issues and I can see that the column shows timestamps as `2023-01-23 12:20:00.000000 UTC`. The same steps as above, using the same Iceberg table, and SPICE, **but using Athena v2 works without any issue**. Any suggestion? Thank you. **UPDATE:** in my Athena v3 based dataset, if I edit the query to exclude the timestamp column and to include a new one as `CAST(CAST(myTimestamp as varchar) as timestamp) as convTimestamp` it works, the data is correctly ingested to SPICE and I can build my analysis. Not the ideal way… ---
**Author:** ![Max](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/max/32/2288_2.png) [@Max](https://community.amazonquick.com/u/Max)\ **Post date:** [January 26, 2023, 6:45pm UTC](https://community.amazonquick.com/t/issues-with-quick-sight-using-athena-v3-and-iceberg-timestamp-columns/9462/2 "2023-01-26T18:45:43Z")
That’s interesting it works on v2 but not v3. You can look into this for further reading. > **[Using unsupported or custom dates - Amazon QuickSight](https://docs.aws.amazon.com/quicksight/latest/user/using-unsupported-dates.html)** > > Use a custom format to import unsupported datetime, date, or time data types. ---
**Author:** ![emilyzhu](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/emilyzhu/32/255_2.png) [@emilyzhu](https://community.amazonquick.com/u/emilyzhu)\ **Post date:** [February 6, 2023, 7:46pm UTC](https://community.amazonquick.com/t/issues-with-quick-sight-using-athena-v3-and-iceberg-timestamp-columns/9462/3 "2023-02-06T19:46:27Z")
cc @yubozhao for help. Is that a known limitation for Athena V3? ---
**Author:** ![emilyzhu](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/emilyzhu/32/255_2.png) [@emilyzhu](https://community.amazonquick.com/u/emilyzhu)\ **Post date:** [February 6, 2023, 9:31pm UTC](https://community.amazonquick.com/t/issues-with-quick-sight-using-athena-v3-and-iceberg-timestamp-columns/9462/4 "2023-02-06T21:31:12Z")
Hi @Antonio_Pintus, do you mind share the datasetID and region? We would like to dig deeper into the problem. You can message me directly if you don’t want to share in the post. Thanks! ---
**Author:** ![yubozhao](https://avatars.discourse-cdn.com/v4/letter/y/8e7dd6/32.png) [@yubozhao](https://community.amazonquick.com/u/yubozhao)\ **Post date:** [February 8, 2023, 12:29am UTC](https://community.amazonquick.com/t/issues-with-quick-sight-using-athena-v3-and-iceberg-timestamp-columns/9462/5 "2023-02-08T00:29:09Z")
We will need the dataset ID to look into this issue. ---
**Author:** ![alberto.serra](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/alberto.serra/32/8129_2.png) [@alberto.serra](https://community.amazonquick.com/u/alberto.serra)\ **Post date:** [April 13, 2023, 10:32am UTC](https://community.amazonquick.com/t/issues-with-quick-sight-using-athena-v3-and-iceberg-timestamp-columns/9462/6 "2023-04-13T10:32:01Z")
Hello, I have the same problem using athena v3 and quicksight with SPICE. Is there any news about this issue? thank you ---
**Author:** ![Antonio\_Pintus](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/antonio_pintus/32/3160_2.png) [@Antonio\_Pintus](https://community.amazonquick.com/u/Antonio_Pintus)\ **Post date:** [April 13, 2023, 1:15pm UTC](https://community.amazonquick.com/t/issues-with-quick-sight-using-athena-v3-and-iceberg-timestamp-columns/9462/7 "2023-04-13T13:15:55Z")
Hi, are there any news about this topic? I can confirm that the issue with Iceberg timestamps is raised in Quick Sight **only** using an **Athena v3 and SPICE** dataset, Athena v3 in Direct Query mode is ok, and Athena v2 both in Direct Query mode and SPICE are ok. @emilyzhu, did you received the datasetID and region I’ve sent in a direct message? Many thanks again! Have a nice day. ---
**Author:** ![d\_markow](https://avatars.discourse-cdn.com/v4/letter/d/e56c9b/32.png) [@d\_markow](https://community.amazonquick.com/u/d_markow)\ **Post date:** [July 10, 2023, 8:54am UTC](https://community.amazonquick.com/t/issues-with-quick-sight-using-athena-v3-and-iceberg-timestamp-columns/9462/8 "2023-07-10T08:54:48Z")
This issue is still present. Do you know if and when this will be resolved?