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 2014/10/08 01:11:34 UTC
[jira] [Commented] (SPARK-3654) Implement all extended HiveQL
statements/commands with a separate parser combinator
[ https://issues.apache.org/jira/browse/SPARK-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162757#comment-14162757 ]
Apache Spark commented on SPARK-3654:
-------------------------------------
User 'liancheng' has created a pull request for this issue:
https://github.com/apache/spark/pull/2698
> 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