QnaList > Groups > Impala-User > Apr 2016
faq

Impala Does Not Store Or Interpret Timestamps Using The Local Timezone

http://www.cloudera.com/documentation/archive/impala/2-x/2-1-x/topics/impala_langref_unsupported.html?scroll=langref_hiveql_delta
   - *Impala does not store or interpret timestamps using the local 
   timezone*, to avoid undesired results from unexpected time zone issues. 
   Timestamps are stored and interpreted relative to UTC. This difference can 
   produce different results for some calls to similarly named date/time 
   functions between Impala and Hive. See Impala Date and Time Functions 
    for details about the Impala functions."
Any plans to fix this?
We currently load all data using Hive and Spark and query from Impala. This 
Impala's inconsistency with what Spark and Hive does gives a lot of 
problems that we don't know how to fix..
It would be great to at least have a session- or server-level setting to 
control this Impala's timestamp problem.
Is there any JIRA for this to fix or implement or workaround?
Thanks,
Ruslan
You received this message because you are subscribed to the Google Groups "Impala User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]

asked Apr 7 2016 at 13:18

Ruslan Dautkhanov 's gravatar image



2 Replies for : Impala Does Not Store Or Interpret Timestamps Using The Local Timezone
It seems this one - https://issues.cloudera.org/browse/IMPALA-1773
This incompatibility bug makes timestamp datatype useless in Impala.
We have time in Impala jumping +7/8 hours (Mountain time), even though
original time
was always 00:00:00. We use Hive/Spark when load data to Hadoop, and
tried to use "UTC" or "America/Denver" during loads, but can't make time on
Impala
side to be consistent / fixed to 00:00:00 as in source systems.
Ruslan Dautkhanov
You received this message because you are subscribed to the Google Groups "Impala User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]

answered Apr 7 2016 at 13:33

Ruslan Dautkhanov 's gravatar image


Hi Ruslan,
I think you want to use the startup flag -convert_legacy_hive_parquet_utc_timestamps=true. More information can be found at http://www.cloudera.com/documentation/enterprise/latest/topics/impala_timestamp.html . Let me know if you have questions.
Casey
It seems this one - https://issues.cloudera.org/browse/IMPALA-1773
This incompatibility bug makes timestamp datatype useless in Impala.
We have time in Impala jumping +7/8 hours (Mountain time), even though original time
was always 00:00:00. We use Hive/Spark when load data to Hadoop, and 
tried to use "UTC" or "America/Denver" during loads, but can't make time on Impala
side to be consistent / fixed to 00:00:00 as in source systems.
Ruslan Dautkhanov
http://www.cloudera.com/documentation/archive/impala/2-x/2-1-x/topics/impala_langref_unsupported.html?scroll=langref_hiveql_delta
Impala does not store or interpret timestamps using the local timezone, to avoid undesired results from unexpected time zone issues. Timestamps are stored and interpreted relative to UTC. This difference can produce different results for some calls to similarly named date/time functions between Impala and Hive. See Impala Date and Time Functions for details about the Impala functions."
Any plans to fix this?
We currently load all data using Hive and Spark and query from Impala. This Impala's inconsistency with what Spark and Hive does gives a lot of problems that we don't know how to fix..
It would be great to at least have a session- or server-level setting to control this Impala's timestamp problem.
Is there any JIRA for this to fix or implement or workaround?
Thanks,
Ruslan
You received this message because you are subscribed to a topic in the Google Groups "Impala User" group.
To unsubscribe from this topic, visit https://groups.google.com/a/cloudera.org/d/topic/impala-user/coolV_m430Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [email protected]
You received this message because you are subscribed to the Google Groups "Impala User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]
You received this message because you are subscribed to the Google Groups "Impala User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]

answered Apr 7 2016 at 13:37

Casey Ching 's gravatar image


Related discussions

Tagged

Group Impala-user

asked Apr 7 2016 at 13:18

active Apr 7 2016 at 13:37

posts:3

users:2

Impala-user

©2013 QnaList.com