[jira] [Resolved] (SPARK-3654) Implement all extended HiveQL statements/commands with a separate parser combinator

["Michael Armbrust (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Armbrust resolved SPARK-3654.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0

Issue resolved by pull request 2590
[https://github.com/apache/spark/pull/2590]

> Implement all extended HiveQL statements/commands with a separate parser combinator
> -----------------------------------------------------------------------------------
>
>                 Key: SPARK-3654
>                 URL: https://issues.apache.org/jira/browse/SPARK-3654
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.1.0
>            Reporter: Cheng Lian
>             Fix For: 1.2.0
>
>
> Statements and commands like {{SET}}, {{CACHE TABLE}} and {{ADD JAR}} etc. are currently parsed in a quite hacky way, like this:
> {code}
> if (sql.trim.toLowerCase.startsWith("cache table")) {
>   sql.trim.toLowerCase.startsWith("cache table") match {
>     ...
>   }
> }
> {code}
> It would be much better to add an extra parser combinator that parses these syntax extensions first, and then fallback to the normal Hive parser.



--
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