[
https://issues.apache.org/jira/browse/PHOENIX-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17441376#comment-17441376
]
Daniel Wong commented on PHOENIX-4922:
--------------------------------------
I was looking at some issues in beginner/noob and saw this one. Probably the
big date/time project that was being done might resolve this. [~stoty] I can't
remember who was leading those changes maybe can we consolidate/remove
duplicate issues? There is Phoenix-5066 this and maybe some more? I've
removed the beginner themes from this as there was some discussion on how to
resolve.
> CONVERT_TZ with date 0001-01-01
> -------------------------------
>
> Key: PHOENIX-4922
> URL: https://issues.apache.org/jira/browse/PHOENIX-4922
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.0
> Environment: SLF4J: Found binding in
> [jar:file:/opt/cloudera/parcels/APACHE_PHOENIX-4.14.0-cdh5.14.2.p0.3/lib/phoenix/phoenix-4.14.0-cdh5.14.2-client.jar!/org/slf4j/impl/StaticLoggerBinder.class]
>
> Reporter: Eduardo
> Priority: Major
> Labels: beginner
>
> Hi all,
> We are storing dates from DB2 (field is a DATE) to Phoenix (Field is a
> DATE) and the conversion function CONVERT_TZ is handle this way with this
> three different records:
> 1) Only "select FECSALDO from table;" without conversion
> 2011-05-16 23:00:00.000 (this is summer time date)
> 2016-03-02 00:00:00.000 (this is winter time date)
> 0001-01-01 00:00:00.000
> 2) Using
> "select CONVERT_TZ(FECSALDO, 'UTC', 'Europe/London') AS FECSALDO from table";
> 2011-05-17 00:00:00.000 -> OK
> 2016-03-02 00:00:00.000 -> OK
> {color:#FF0000}0001-12-31 23:58:45.000 . -> WTF{color}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
