[jira] [Assigned] (SPARK-22934) Make optional clauses order insensitive for CREATE TABLE SQL statement

2017-12-31 Thread Apache Spark (JIRA)

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

Apache Spark reassigned SPARK-22934:


Assignee: Apache Spark  (was: Xiao Li)

> Make optional clauses order insensitive for CREATE TABLE SQL statement
> --
>
> Key: SPARK-22934
> URL: https://issues.apache.org/jira/browse/SPARK-22934
> Project: Spark
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 2.2.1
>Reporter: Xiao Li
>Assignee: Apache Spark
>
> Each time, when I write a complex Create Table statement, I have to open the 
> .g4 file to find the EXACT order of clauses in CREATE TABLE statement. When 
> the order is not right, I will get A strange confusing error message 
> generated from ALTR4. 
> {noformat}
> CREATE [TEMPORARY] TABLE [IF NOT EXISTS] [db_name.]table_name
> [(col_name1 col_type1 [COMMENT col_comment1], ...)]
> USING datasource
> [OPTIONS (key1=val1, key2=val2, ...)]
> [PARTITIONED BY (col_name1, col_name2, ...)]
> [CLUSTERED BY (col_name3, col_name4, ...) INTO num_buckets BUCKETS]
> [LOCATION path]
> [COMMENT table_comment]
> [TBLPROPERTIES (key1=val1, key2=val2, ...)]
> [AS select_statement]
> {noformat}
> The proposal is to make the following clauses order insensitive. 
> {noformat}
> [OPTIONS (key1=val1, key2=val2, ...)]
> [PARTITIONED BY (col_name1, col_name2, ...)]
> [CLUSTERED BY (col_name3, col_name4, ...) INTO num_buckets BUCKETS]
> [LOCATION path]
> [COMMENT table_comment]
> [TBLPROPERTIES (key1=val1, key2=val2, ...)]
> {noformat}
> The same idea is also applicable to Create Hive Table. 
> {noformat}
> CREATE [EXTERNAL] TABLE [IF NOT EXISTS] [db_name.]table_name
> [(col_name1[:] col_type1 [COMMENT col_comment1], ...)]
> [COMMENT table_comment]
> [PARTITIONED BY (col_name2[:] col_type2 [COMMENT col_comment2], ...)]
> [ROW FORMAT row_format]
> [STORED AS file_format]
> [LOCATION path]
> [TBLPROPERTIES (key1=val1, key2=val2, ...)]
> [AS select_statement]
> {noformat}
> The proposal is to make the following clauses order insensitive. 
> {noformat}
> [COMMENT table_comment]
> [PARTITIONED BY (col_name2[:] col_type2 [COMMENT col_comment2], ...)]
> [ROW FORMAT row_format]
> [STORED AS file_format]
> [LOCATION path]
> [TBLPROPERTIES (key1=val1, key2=val2, ...)]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org



[jira] [Assigned] (SPARK-22934) Make optional clauses order insensitive for CREATE TABLE SQL statement

2017-12-31 Thread Apache Spark (JIRA)

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

Apache Spark reassigned SPARK-22934:


Assignee: Xiao Li  (was: Apache Spark)

> Make optional clauses order insensitive for CREATE TABLE SQL statement
> --
>
> Key: SPARK-22934
> URL: https://issues.apache.org/jira/browse/SPARK-22934
> Project: Spark
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 2.2.1
>Reporter: Xiao Li
>Assignee: Xiao Li
>
> Each time, when I write a complex Create Table statement, I have to open the 
> .g4 file to find the EXACT order of clauses in CREATE TABLE statement. When 
> the order is not right, I will get A strange confusing error message 
> generated from ALTR4. 
> {noformat}
> CREATE [TEMPORARY] TABLE [IF NOT EXISTS] [db_name.]table_name
> [(col_name1 col_type1 [COMMENT col_comment1], ...)]
> USING datasource
> [OPTIONS (key1=val1, key2=val2, ...)]
> [PARTITIONED BY (col_name1, col_name2, ...)]
> [CLUSTERED BY (col_name3, col_name4, ...) INTO num_buckets BUCKETS]
> [LOCATION path]
> [COMMENT table_comment]
> [TBLPROPERTIES (key1=val1, key2=val2, ...)]
> [AS select_statement]
> {noformat}
> The proposal is to make the following clauses order insensitive. 
> {noformat}
> [OPTIONS (key1=val1, key2=val2, ...)]
> [PARTITIONED BY (col_name1, col_name2, ...)]
> [CLUSTERED BY (col_name3, col_name4, ...) INTO num_buckets BUCKETS]
> [LOCATION path]
> [COMMENT table_comment]
> [TBLPROPERTIES (key1=val1, key2=val2, ...)]
> {noformat}
> The same idea is also applicable to Create Hive Table. 
> {noformat}
> CREATE [EXTERNAL] TABLE [IF NOT EXISTS] [db_name.]table_name
> [(col_name1[:] col_type1 [COMMENT col_comment1], ...)]
> [COMMENT table_comment]
> [PARTITIONED BY (col_name2[:] col_type2 [COMMENT col_comment2], ...)]
> [ROW FORMAT row_format]
> [STORED AS file_format]
> [LOCATION path]
> [TBLPROPERTIES (key1=val1, key2=val2, ...)]
> [AS select_statement]
> {noformat}
> The proposal is to make the following clauses order insensitive. 
> {noformat}
> [COMMENT table_comment]
> [PARTITIONED BY (col_name2[:] col_type2 [COMMENT col_comment2], ...)]
> [ROW FORMAT row_format]
> [STORED AS file_format]
> [LOCATION path]
> [TBLPROPERTIES (key1=val1, key2=val2, ...)]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org