spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SPARK-24151) CURRENT_DATE, CURRENT_TIMESTAMP incorrectly resolved as column names when caseSensitive is enabled
Date Wed, 02 May 2018 16:00:02 GMT
James Thompson created SPARK-24151:
--------------------------------------

             Summary: CURRENT_DATE, CURRENT_TIMESTAMP incorrectly resolved as column names
when caseSensitive is enabled
                 Key: SPARK-24151
                 URL: https://issues.apache.org/jira/browse/SPARK-24151
             Project: Spark
          Issue Type: Bug
          Components: SQL
    Affects Versions: 2.3.0
            Reporter: James Thompson


After this change: https://issues.apache.org/jira/browse/SPARK-22333

Running SQL such as "CURRENT_TIMESTAMP" can fail spark.sql.caseSensitive has been enabled:
{code:java}
org.apache.spark.sql.AnalysisException: cannot resolve '`CURRENT_TIMESTAMP`' given input columns: [col1]{code}
This is due to the fact that the analyzer incorrectly uses a case sensitive resolver to resolve
the function. I will submit a PR with a fix + test for this.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message