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 2017/10/23 11:52:00 UTC
[jira] [Commented] (SPARK-22333) ColumnReference should get higher
priority than timeFunctionCall(CURRENT_DATE, CURRENT_TIMESTAMP)
[ https://issues.apache.org/jira/browse/SPARK-22333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214999#comment-16214999 ]
Apache Spark commented on SPARK-22333:
--------------------------------------
User 'DonnyZone' has created a pull request for this issue:
https://github.com/apache/spark/pull/19559
> ColumnReference should get higher priority than timeFunctionCall(CURRENT_DATE, CURRENT_TIMESTAMP)
> -------------------------------------------------------------------------------------------------
>
> Key: SPARK-22333
> URL: https://issues.apache.org/jira/browse/SPARK-22333
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.1.0, 2.1.1, 2.1.2, 2.2.0
> Reporter: Feng Zhu
>
> In our cluster, there is a table "T" with column named as "current_date". When we select data from this column with SQL:
> {code:sql}
> select current_date from T
> {code}
> We get the wrong answer, as the column is translated as CURRENT_DATE() function.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org