[
https://issues.apache.org/jira/browse/SPARK-11817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012262#comment-15012262
]
Yin Huai commented on SPARK-11817:
----------------------------------
Here is an example. In 1.5 and 1.6, we have
{code}
scala> sqlContext.sql("select cast('1970-01-01 00:00:00.123456789' as
timestamp), cast('1970-01-01 00:00:00.123456' as timestamp)").show(10, false)
+----+--------------------------+
|_c0 |_c1 |
+----+--------------------------+
|null|1970-01-01 00:00:00.123456|
+----+--------------------------+
{code}
In 1.4, we have
{code}
sqlContext.sql("select cast('1970-01-01 00:00:00.123456789' as timestamp),
cast('1970-01-01 00:00:00.123456' as timestamp)").collect
res7: Array[org.apache.spark.sql.Row] = Array([1970-01-01
00:00:00.123456789,1970-01-01 00:00:00.123456])
{code}
> insert of timestamp with factional seconds inserts a NULL
> ---------------------------------------------------------
>
> Key: SPARK-11817
> URL: https://issues.apache.org/jira/browse/SPARK-11817
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.5.1
> Reporter: Chip Sands
>
> Using the Thrift jdbc interface.
> The insert of the value of "1970-01-01 00:00:00.123456789" to a timestamp
> column, inserts a NULL into the database. I am aware the of the change
> From 1.5 releases notes Timestamp Type’s precision is reduced to 1
> microseconds (1us). However, to be compatible with previous versions, I
> would suggest either rounding or truncating the fractional seconds not
> inserting a NULL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
