You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/03/22 09:03:00 UTC

[jira] [Resolved] (SPARK-27212) Eliminate TimeZone to ZoneId conversion in stringToTimestamp

     [ https://issues.apache.org/jira/browse/SPARK-27212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyukjin Kwon resolved SPARK-27212.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0

Issue resolved by pull request 24155
[https://github.com/apache/spark/pull/24155]

> Eliminate TimeZone to ZoneId conversion in stringToTimestamp
> ------------------------------------------------------------
>
>                 Key: SPARK-27212
>                 URL: https://issues.apache.org/jira/browse/SPARK-27212
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.4.0
>            Reporter: Maxim Gekk
>            Assignee: Maxim Gekk
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> The stringToTimestamp method of DateTimeUtils (and stringToDate as well) can be called per each row. And the method converts TimeZone to ZoneId each time. The operation is relatively expensive because it does intermediate conversion to a string: http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/f940e7a48b72/src/share/classes/java/util/TimeZone.java#l547
> The conversion is unnecessary, and could be avoid. The ticket aims to replace signature of stringToTimestamp to require ZoneId as a parameter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org