spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Takeshi Yamamuro (JIRA)" <>
Subject [jira] [Commented] (SPARK-26215) define reserved keywords after SQL standard
Date Mon, 03 Dec 2018 12:10:00 GMT


Takeshi Yamamuro commented on SPARK-26215:

These reserved words should be handled inside SqlBase.g4? It seems postgresql do so

> define reserved keywords after SQL standard
> -------------------------------------------
>                 Key: SPARK-26215
>                 URL:
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 2.4.0
>            Reporter: Wenchen Fan
>            Priority: Major
> There are 2 kinds of SQL keywords: reserved and non-reserved. Reserved keywords can't
be used as identifiers.
> In Spark SQL, we are too tolerant about non-reserved keywors. A lot of keywords are non-reserved
and sometimes it cause ambiguity (IIRC we hit a problem when improving the INTERVAL syntax).
> I think it will be better to just follow other databases or SQL standard to define reserved
keywords, so that we don't need to think very hard about how to avoid ambiguity.
> For reference:

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message