[
https://issues.apache.org/jira/browse/HIVE-21349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Ivanfi updated HIVE-21349:
---------------------------------
Description:
As specified in the [design doc for TIMESTAMP
types|https://cwiki.apache.org/confluence/display/Hive/Different+TIMESTAMP+types],
the TIMESTAMP WITHOUT TIME ZONE type shall behave like the
[LocalDateTime|https://docs.oracle.com/javase/8/docs/api/java/time/LocalDateTime.html]
class of Java, i.e., each value is a recording of what can be seen on a
calendar and a clock hanging on the wall, for example "1969-07-20 16:17:39". It
can be decomposed into year, month, day, hour, minute and seconds fields, but
with no time zone information available, it does not correspond to any specific
point in time.
This behaviour is consistent with the SQL standard (revisions 2003 and higher).
was:
As specified in the [design doc for TIMESTAMP
types|https://cwiki.apache.org/confluence/display/Hive/Different+TIMESTAMP+types],
the TIMESTAMP WITHOUT TIME ZONE type shall behave like the LocalDateTime class
of Java, i.e., each value is a recording of what can be seen on a calendar and
a clock hanging on the wall, for example "1969-07-20 16:17:39". It can be
decomposed into year, month, day, hour, minute and seconds fields, but with no
time zone information available, it does not correspond to any specific point
in time.
This behaviour is consistent with the SQL standard (revisions 2003 and higher).
> TIMESTAMP WITHOUT TIME ZONE
> ---------------------------
>
> Key: HIVE-21349
> URL: https://issues.apache.org/jira/browse/HIVE-21349
> Project: Hive
> Issue Type: Task
> Reporter: Zoltan Ivanfi
> Priority: Major
>
> As specified in the [design doc for TIMESTAMP
> types|https://cwiki.apache.org/confluence/display/Hive/Different+TIMESTAMP+types],
> the TIMESTAMP WITHOUT TIME ZONE type shall behave like the
> [LocalDateTime|https://docs.oracle.com/javase/8/docs/api/java/time/LocalDateTime.html]
> class of Java, i.e., each value is a recording of what can be seen on a
> calendar and a clock hanging on the wall, for example "1969-07-20 16:17:39".
> It can be decomposed into year, month, day, hour, minute and seconds fields,
> but with no time zone information available, it does not correspond to any
> specific point in time.
> This behaviour is consistent with the SQL standard (revisions 2003 and
> higher).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
