You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Maxim Gekk (Jira)" <ji...@apache.org> on 2020/09/01 11:56:00 UTC
[jira] [Commented] (SPARK-32637) SPARK SQL JDBC truncates last
value of seconds for datetime2 values for Azure SQL DB
[ https://issues.apache.org/jira/browse/SPARK-32637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188384#comment-17188384 ]
Maxim Gekk commented on SPARK-32637:
------------------------------------
Spark's TIMESTAMP type has microsecond precision. This is by design and it is not a bug.
> SPARK SQL JDBC truncates last value of seconds for datetime2 values for Azure SQL DB
> -------------------------------------------------------------------------------------
>
> Key: SPARK-32637
> URL: https://issues.apache.org/jira/browse/SPARK-32637
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.4.1
> Reporter: Mohit Dave
> Priority: Major
>
> SPARK jdbc is truncating TIMESTAMP values for the microsecond when datetime2 datatype is used for Microsoft SQL Server JDBC driver.
>
> Source data(datetime2) : '2007-08-08 12:35:29.1234567'
>
> After loading to target using SPARK dataframes
>
> Target data(datetime2) : '2007-08-08 12:35:29.1234560'
>
--
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