[
https://issues.apache.org/jira/browse/HIVE-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Sharma resolved HIVE-2557.
---------------------------------
Resolution: Duplicate
fixed as part of - https://issues.apache.org/jira/browse/HIVE-25306
> Inserting illegal timestamp behaves differently that in MySql
> -------------------------------------------------------------
>
> Key: HIVE-2557
> URL: https://issues.apache.org/jira/browse/HIVE-2557
> Project: Hive
> Issue Type: Bug
> Reporter: Robert Surówka
> Assignee: Ashish Sharma
> Priority: Trivial
>
> In MySql there is:
> Illegal DATETIME, DATE, or TIMESTAMP values are converted to the "zero" value
> of the appropriate type ('0000-00-00 00:00:00' or '0000-00-00'). (
> http://dev.mysql.com/doc/refman/5.1/en/datetime.html ), yet in Hive we have
> e.g.:
> hive> insert into table rrt select '1970-01-51 00:00:05' from src_copy limit
> 1;
> hive> select * from rrt;
> 1970-02-20 00:00:05
> It is probably something to be discussed whether to change it, but at least
> we should be aware of this current inconsistency, especially when
> documentation for timestamp will be added.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
