Support Questions

Find answers, ask questions, and share your expertise
Announcements
Now Live: Explore expert insights and technical deep dives on the new Cloudera Community BlogsRead the Announcement

Who agreed with this topic

How to handle out of range timestamps for impala with parquet format?

avatar
New Contributor

I tried creating a table with the following command:

 

create table foo
stored as parquet
as
select cast('0001-01-01 00:00:00' as timestamp) ts;

If I launch such command in Impala, the timestamp becomes a NULL value and from that moment on both Hive and Impala see the content as NULL. However, if I create the table using Hive the timestamp is preserved and I can see it correctly within Hive, but Impala shows the following error:

 

Year is out of valid range: 1400..10000

How can I handle this issue? I need both parquet format and the Impala connection.

 

Who agreed with this topic