[jira] [Commented] (SPARK-17035) Conversion of datetime.max to microseconds produces incorrect value

["Dongjoon Hyun (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420086#comment-15420086 ] 

Dongjoon Hyun commented on SPARK-17035:
---------------------------------------

Hi, [~ptkool].
You're right. It seems the microsecond part of `Timestamp` type is lost.
I'll make a PR for this issue soon.

> Conversion of datetime.max to microseconds produces incorrect value
> -------------------------------------------------------------------
>
>                 Key: SPARK-17035
>                 URL: https://issues.apache.org/jira/browse/SPARK-17035
>             Project: Spark
>          Issue Type: Bug
>          Components: PySpark
>    Affects Versions: 2.0.0
>            Reporter: Michael Styles
>            Priority: Minor
>
> Conversion of datetime.max to microseconds produces incorrect value. For example,
> {noformat}
> from datetime import datetime
> from pyspark.sql import Row
> from pyspark.sql.types import StructType, StructField, TimestampType
> schema = StructType([StructField("dt", TimestampType(), False)])
> data = [{"dt": datetime.max}]
> # convert python objects to sql data
> sql_data = [schema.toInternal(row) for row in data]
> # Value is wrong.
> sql_data
> [(2.534023188e+17,)]
> {noformat}
> This value should be [(253402318799999999,)].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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