[
https://issues.apache.org/jira/browse/HIVE-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236736#comment-13236736
]
Michael Ubell commented on HIVE-2558:
-------------------------------------
In the query:
select * from rrt where r = '1970-01-01 00:00:01';
you say that the problem is that the field is treated as a string not as a time
stamp but if it is treated as a string then either there should be a proper
conversion of the string to timestamp (or vice versa) to do the compare or an
error should be raised, you cannot just compare the bytes (or what ever hive is
doing) and return an invalid answer.
The first query:
select * from rrt where r in ('1970-01-01 00:00:01');
does the right thing:
FAILED: Error in semantic analysis: Line 1:26 Wrong arguments ''1970-01-01
00:00:01'': The arguments for IN should be the same type! Types are: {timestamp
IN (string)}
> 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
