Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-24151

CURRENT_DATE, CURRENT_TIMESTAMP incorrectly resolved as column names when caseSensitive is enabled

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.2.1, 2.3.0
    • 2.4.0
    • SQL
    • None

    Description

      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:

      org.apache.spark.sql.AnalysisException: cannot resolve '`CURRENT_TIMESTAMP`' given input columns: [col1]

      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.

       

      Attachments

        Issue Links

          Activity

            People

              jamesthomp James Thompson
              jamesthomp James Thompson
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: