[
https://issues.apache.org/jira/browse/SPARK-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398424#comment-15398424
]
holdenk commented on SPARK-16774:
---------------------------------
While diving into this (relatedly I hate timezones) - I'm pretty sure I've
encountered a logic bug for our handling close to timezone boundaries - namely
the inline comments suggest the timestamp is being constructed against UTC but
careful reading of the JDK code indicates its actually using the system
default. I'm going to add some tests around this and replace the fall-back code
with the calendar based approach.
> Fix use of deprecated TimeStamp constructor
> -------------------------------------------
>
> Key: SPARK-16774
> URL: https://issues.apache.org/jira/browse/SPARK-16774
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Reporter: holdenk
>
> The TimeStamp constructor we use inside of DateTime utils has been deprecated
> since JDK 1.1 - while Java does take a long time to remove deprecated
> functionality we might as well address this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
