[
https://issues.apache.org/jira/browse/DRILL-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583842#comment-14583842
]
Venkata krishnan Sowrirajan commented on DRILL-3284:
----------------------------------------------------
I think Drill itself have a unix_timestamp() and we no more use hive
unix_timestamp(). As far as unix_timestamp() is concerned, it gets current Unix
timestamp in seconds both in Hive as well as Drill.
Refer to unix_timestamp() in hive in the below link:
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF
> Document incompatibility between drill's to_date and hive's unix_timestamp
> --------------------------------------------------------------------------
>
> Key: DRILL-3284
> URL: https://issues.apache.org/jira/browse/DRILL-3284
> Project: Apache Drill
> Issue Type: Bug
> Components: Documentation, Functions - Hive
> Reporter: Rahul Challapalli
> Assignee: Bridget Bevens
>
> The below query from drill produces wrong results because unix_timestamp
> (function from hive) returns the value in seconds while to_date treats its
> input in milliseconds.
> {code}
> select to_date(unix_timestamp('1998-05-06', 'yyyy-MM-dd')) from dummy limit 1;
> +-------------+
> | EXPR$0 |
> +-------------+
> | 1970-01-11 |
> +-------------+
> {code}
> In order to make this work we should use the below query
> {code}
> select to_date(unix_timestamp('1998-05-06', 'yyyy-MM-dd')*1000) from dummy
> limit 1;
> +-------------+
> | EXPR$0 |
> +-------------+
> | 1998-05-06 |
> +-------------+
> {code}
> If this is not a bug on drill's side, we should atleast document this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
