You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/04/24 10:12:39 UTC
[jira] [Assigned] (SPARK-7098) Inconsistent Timestamp behavior when
used in WHERE clause
[ https://issues.apache.org/jira/browse/SPARK-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned SPARK-7098:
-----------------------------------
Assignee: (was: Apache Spark)
> Inconsistent Timestamp behavior when used in WHERE clause
> ---------------------------------------------------------
>
> Key: SPARK-7098
> URL: https://issues.apache.org/jira/browse/SPARK-7098
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.2.1
> Environment: Windows, Linux, Mac OS X with Java 1.7
> Reporter: Peter Hagelund
>
> java.sql.Timestamps containing a nano value of 0 are not matched in a WHERE clause like SELECT ... FROM ... WHERE TS_COL = '2015-04-23 02:55:00.0'. When used with an explicit cast like SELECT ... FROM ... WHERE TS_COL = CAST('2015-04-23 02:55:00.0' AS TIMESTAMP) things work as expected.
--
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