[
https://issues.apache.org/jira/browse/HIVE-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168407#comment-13168407
]
Priyadarshini commented on HIVE-2558:
-------------------------------------
Hi Robert,
In the above query, timestamp is used as a column datatype of the table rrt.
So when u want to use the timestamp in the where clause of select statement, we
should be able to tell that the data we are searching is a timestamp value.
Giving the field value in single/double quote will be treated as a string value
and not timestamp value.
So when u wanted to retreive the results that satisfy the timestamp value you
are specifying in where clause, the query should be
select * from rrt where r = unix_timestamp('1970-01-01 00:00:01');
This would be interpreted as data u r searching is a timestamp.
Hope it helps
Thanks,
Priya
> Timestamp comparisons don't work
> --------------------------------
>
> Key: HIVE-2558
> URL: https://issues.apache.org/jira/browse/HIVE-2558
> Project: Hive
> Issue Type: Bug
> Reporter: Robert Surówka
>
> I may be missing something, but:
> After performing:
> create table rrt (r timestamp);
> insert into table rrt select '1970-01-01 00:00:01' from src limit 1;
> Following queries give undesirable results:
> select * from rrt where r in ('1970-01-01 00:00:01');
> select * from rrt where r in (0);
> select * from rrt where r = 0;
> select * from rrt where r = '1970-01-01 00:00:01';
> At least for the first two, the reason may be the lack of timestamp in
> numericTypes Map from FunctionRegistry.java (591) . Yet whether we really
> want to have a linear hierarchy of primitive types in the end, is another
> question.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
