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/01/02 00:02:00 UTC
[jira] [Resolved] (SPARK-26374) Support new date/timestamp parser
in HadoopFsRelationTest
[ https://issues.apache.org/jira/browse/SPARK-26374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-26374.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 23417
[https://github.com/apache/spark/pull/23417]
> Support new date/timestamp parser in HadoopFsRelationTest
> ---------------------------------------------------------
>
> Key: SPARK-26374
> URL: https://issues.apache.org/jira/browse/SPARK-26374
> Project: Spark
> Issue Type: Bug
> Components: SQL, Tests
> Affects Versions: 2.4.0
> Reporter: Maxim Gekk
> Assignee: Maxim Gekk
> Priority: Minor
> Fix For: 3.0.0
>
>
> The *test all data types* test uses the legacy parser for dates/timestamps (https://github.com/apache/spark/pull/23196/files#diff-3986f801dd1335af3f300b006a03e987R129). The test is passed on UTC timezone and new parser but fails on different timezones ([see|https://github.com/apache/spark/pull/23196#discussion_r241492360]):
> {code}
> == Correct Answer - 10 == == Spark Answer - 10 ==
> ...
> ![10,1670-02-11 14:09:54.746] [10,1670-02-11 14:08:56.746]
> == Correct Answer - 10 == == Spark Answer - 10 ==
> [1,6246-07-23 20:34:56.968] [1,6246-07-23 20:34:56.968]
> ![2,0109-07-20 18:38:03.788] [2,0109-07-20 18:37:05.788]
> {code}
> The ticket aims to switching on new parser independently from timezones.
--
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