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

Posted to issues@spark.apache.org by "Ruifeng Zheng (Jira)" <ji...@apache.org> on 2026/01/29 01:32:00 UTC

[jira] [Resolved] (SPARK-55225) Fix timestamp unit issue for pandas 3

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

Ruifeng Zheng resolved SPARK-55225.
-----------------------------------
    Fix Version/s: 4.2.0
       Resolution: Fixed

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

> Fix timestamp unit issue for pandas 3
> -------------------------------------
>
>                 Key: SPARK-55225
>                 URL: https://issues.apache.org/jira/browse/SPARK-55225
>             Project: Spark
>          Issue Type: Sub-task
>          Components: PySpark
>    Affects Versions: 4.2.0
>            Reporter: Tian Gao
>            Assignee: Tian Gao
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.2.0
>
>
> pandas 3 has different default resolution for datetime types. Currently we can't match it because we always convert `TimestampType` to `datetime[ns]`. We don't have an agreed solution here.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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