You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Gengliang Wang (Jira)" <ji...@apache.org> on 2021/06/29 08:58:00 UTC
[jira] [Resolved] (SPARK-35927) Remove type collection
AllTimestampTypes
[ https://issues.apache.org/jira/browse/SPARK-35927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gengliang Wang resolved SPARK-35927.
------------------------------------
Fix Version/s: 3.2.0
Resolution: Fixed
Issue resolved by pull request 33129
[https://github.com/apache/spark/pull/33129]
> Remove type collection AllTimestampTypes
> ----------------------------------------
>
> Key: SPARK-35927
> URL: https://issues.apache.org/jira/browse/SPARK-35927
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.2.0
> Reporter: Gengliang Wang
> Assignee: Gengliang Wang
> Priority: Minor
> Fix For: 3.2.0
>
>
> As discussed in https://github.com/apache/spark/pull/33115#discussion_r659866760, it is more convenient to have a new data type "AnyTimestampType" instead of using type collection `AllTimestampTypes`:
> 1. simplify the pattern match
> 2. In the default type coercion rules, when implicit casting a type to a TypeCollection type, Spark chooses the first convertible data type as the result. If we are going to make the default timestamp type configurable, having AnyTimestampType is better
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org