Github user vdiravka commented on the issue:
https://github.com/apache/drill/pull/600
@parthchandra The known issue with hive that it stores timestamp values
into parquet files with local zone retain. That's why when we want to retrieve
the data from such table we should consider the local timezone.
On the other hand parquet files don't involve the particular time zone and
when we just read the file we shouldn't consdier a local timezone. And this is
also standard drill behaviour with normal int64 timestamps.
So I decided that we need two `IMPALA_TIMESTAMP` functions: for hive and
for regular parquet files.
I left `IMPALA_TIMESTAMP` function without local timezone retain and I
added `IMPALA_TIMESTAMP_LOCALTIMEZONE` function (implicit using with hive
timestamps and enabled drill native parquet reader).
Please let me know if this approach is good.
Changes in a new commit for easy review.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
