[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
---
layout: global
2019-03-18 02:19:52 -04:00
title: Spark SQL Keywords
displayTitle: Spark SQL Keywords
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
---
2019-03-18 02:19:52 -04:00
When `spark.sql.parser.ansi.enabled` is true, Spark SQL has two kinds of keywords:
* Reserved keywords: Keywords that are reserved and can't be used as identifiers for table, view, column, function, alias, etc.
* Non-reserved keywords: Keywords that have a special meaning only in particular contexts and can be used as identifiers in other contexts. For example, `SELECT 1 WEEK` is an interval literal, but WEEK can be used as identifiers in other places.
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
2019-03-18 02:19:52 -04:00
When `spark.sql.parser.ansi.enabled` is false, Spark SQL has two kinds of keywords:
* Non-reserved keywords: Same definition as the one when `spark.sql.parser.ansi.enabled=true` .
* Strict-non-reserved keywords: A strict version of non-reserved keywords, which can not be used as table alias.
By default `spark.sql.parser.ansi.enabled` is false.
Below is a list of all the keywords in Spark SQL.
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< table class = "table" >
< tr > < th rowspan = "2" style = "vertical-align: middle;" > < b > Keyword< / b > < / th > < th colspan = "2" > < b > Spark SQL< / b > < / th > < th rowspan = "2" style = "vertical-align: middle;" > < b > SQL-2011< / b > < / th > < / tr >
< tr > < th > < b > ANSI mode< / b > < / th > < th > < b > default mode< / b > < / th > < / tr >
< tr > < td > ADD< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > AFTER< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > ALL< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ALTER< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ANALYZE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > AND< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > ANTI< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > non-reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > ANY< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ARCHIVE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > ARRAY< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > AS< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ASC< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > AT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > AUTHORIZATION< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > BETWEEN< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > BOTH< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > BUCKET< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > BUCKETS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > BY< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > CACHE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > CASCADE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > CASE< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > CAST< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > CHANGE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > CHECK< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > CLEAR< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > CLUSTER< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > CLUSTERED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > CODEGEN< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > COLLATE< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > COLLECTION< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > COLUMN< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > COLUMNS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > COMMENT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > COMMIT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > COMPACT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > COMPACTIONS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > COMPUTE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > CONCATENATE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > CONSTRAINT< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > COST< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > CREATE< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > CROSS< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > CUBE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > CURRENT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > CURRENT_DATE< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > CURRENT_TIME< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > CURRENT_TIMESTAMP< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > CURRENT_USER< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > DATA< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DATABASE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DATABASES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-13 21:45:29 -04:00
< tr > < td > DAY< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > DAYS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > DBPROPERTIES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DEFINED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DELETE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > DELIMITED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DESC< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DESCRIBE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > DFS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DIRECTORIES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DIRECTORY< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DISTINCT< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > DISTRIBUTE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DIV< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > DROP< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ELSE< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > END< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ESCAPED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > EXCEPT< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > EXCHANGE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > EXISTS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > EXPLAIN< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > EXPORT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > EXTENDED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > EXTERNAL< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > EXTRACT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > FALSE< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > FETCH< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > FIELDS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > FILEFORMAT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > FIRST< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > FOLLOWING< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > FOR< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > FOREIGN< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > FORMAT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > FORMATTED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > FROM< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > FULL< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > FUNCTION< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > FUNCTIONS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > GLOBAL< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > GRANT< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > GROUP< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > GROUPING< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > HAVING< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-13 21:45:29 -04:00
< tr > < td > HOUR< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > HOURS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > IF< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > IGNORE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > IMPORT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > IN< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > INDEX< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > INDEXES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > INNER< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > INPATH< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > INPUTFORMAT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > INSERT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > INTERSECT< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > INTERVAL< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > INTO< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > IS< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ITEMS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > JOIN< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > KEYS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > LAST< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > LATERAL< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > LAZY< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > LEADING< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > LEFT< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > LIKE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > LIMIT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > LINES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > LIST< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > LOAD< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > LOCAL< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > LOCATION< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > LOCK< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > LOCKS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > LOGICAL< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > MACRO< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > MAP< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-13 21:45:29 -04:00
< tr > < td > MICROSECOND< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > MICROSECONDS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > MILLISECOND< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > MILLISECONDS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-19 08:18:40 -04:00
< tr > < td > MINUS< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-13 21:45:29 -04:00
< tr > < td > MINUTE< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > MINUTES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > MONTH< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > MONTHS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > MSCK< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > NATURAL< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > NO< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > NOT< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > NULL< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > NULLS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > OF< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > ON< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > ONLY< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > OPTION< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > OPTIONS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > OR< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ORDER< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > OUT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > OUTER< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > OUTPUTFORMAT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > OVER< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > OVERLAPS< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > OVERWRITE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > PARTITION< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > PARTITIONED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > PARTITIONS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-19 08:18:40 -04:00
< tr > < td > PERCENT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > PIVOT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > POSITION< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > PRECEDING< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > PRIMARY< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > PRINCIPALS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > PURGE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-19 08:18:40 -04:00
< tr > < td > QUERY< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > RANGE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > RECORDREADER< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > RECORDWRITER< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > RECOVER< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > REDUCE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > REFERENCES< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > REFRESH< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > RENAME< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > REPAIR< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > REPLACE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > RESET< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > RESTRICT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > REVOKE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > RIGHT< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > RLIKE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > ROLE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > ROLES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > ROLLBACK< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ROLLUP< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ROW< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > ROWS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > SCHEMA< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-13 21:45:29 -04:00
< tr > < td > SECOND< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > SECONDS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > SELECT< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > SEMI< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > non-reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > SEPARATED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > SERDE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > SERDEPROPERTIES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > SESSION_USER< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > SET< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > SETS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > SHOW< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > SKEWED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > SOME< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > SORT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > SORTED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > START< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > STATISTICS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > STORED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > STRATIFY< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > STRUCT< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > TABLE< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > TABLES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > TABLESAMPLE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > TBLPROPERTIES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > TEMPORARY< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > TERMINATED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > THEN< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > TO< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > TOUCH< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > TRAILING< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > TRANSACTION< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > TRANSACTIONS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > TRANSFORM< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > TRUE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > TRUNCATE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > UNARCHIVE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > UNBOUNDED< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > UNCACHE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > UNION< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > UNIQUE< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > UNLOCK< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > UNSET< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > USE< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > USER< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-18 02:19:52 -04:00
< tr > < td > USING< / td > < td > reserved< / td > < td > strict-non-reserved< / td > < td > reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > VALUES< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > VIEW< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
2019-03-19 08:18:40 -04:00
< tr > < td > WEEK< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
< tr > < td > WEEKS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< tr > < td > WHEN< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > WHERE< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > WINDOW< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > WITH< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
2019-03-13 21:45:29 -04:00
< tr > < td > YEAR< / td > < td > reserved< / td > < td > non-reserved< / td > < td > reserved< / td > < / tr >
< tr > < td > YEARS< / td > < td > non-reserved< / td > < td > non-reserved< / td > < td > non-reserved< / td > < / tr >
[SPARK-26215][SQL] Define reserved/non-reserved keywords based on the ANSI SQL standard
## What changes were proposed in this pull request?
This pr targeted to define reserved/non-reserved keywords for Spark SQL based on the ANSI SQL standards and the other database-like systems (e.g., PostgreSQL). We assume that they basically follow the ANSI SQL-2011 standard, but it is slightly different between each other. Therefore, this pr documented all the keywords in `docs/sql-reserved-and-non-reserved-key-words.md`.
NOTE: This pr only added a small set of keywords as reserved ones and these keywords are reserved in all the ANSI SQL standards (SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011, and SQL-2016) and PostgreSQL. This is because there is room to discuss which keyword should be reserved or not, .e.g., interval units (day, hour, minute, second, ...) are reserved in the ANSI SQL standards though, they are not reserved in PostgreSQL. Therefore, we need more researches about the other database-like systems (e.g., Oracle Databases, DB2, SQL server) in follow-up activities.
References:
- The reserved/non-reserved SQL keywords in the ANSI SQL standards: https://developer.mimer.com/wp-content/uploads/2018/05/Standard-SQL-Reserved-Words-Summary.pdf
- SQL Key Words in PostgreSQL: https://www.postgresql.org/docs/current/sql-keywords-appendix.html
## How was this patch tested?
Added tests in `TableIdentifierParserSuite`.
Closes #23259 from maropu/SPARK-26215-WIP.
Authored-by: Takeshi Yamamuro <yamamuro@apache.org>
Signed-off-by: Takeshi Yamamuro <yamamuro@apache.org>
2019-02-22 18:38:47 -05:00
< / table >
