You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2019/02/03 00:21:00 UTC

[jira] [Resolved] (SPARK-26805) Eliminate double checking of stringToDate and stringToTimestamp inputs

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

Sean Owen resolved SPARK-26805.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0

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

> Eliminate double checking of stringToDate and stringToTimestamp inputs
> ----------------------------------------------------------------------
>
>                 Key: SPARK-26805
>                 URL: https://issues.apache.org/jira/browse/SPARK-26805
>             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 LocalTime and LocalTime classes as well as other java.time classes used inside of stringToTimestamp and stringToDate do checking of input parameters already. There is no need to do that twice. The ticket aims to remove isInvalidDate() from DateTimeUtils and eliminate such double checking. 



--
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