[
https://issues.apache.org/jira/browse/FLINK-27237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dalongliu updated FLINK-27237:
------------------------------
Description:
This is an umbrella issue which is used to discuss the syntax enhancement about
partitioned table. These new syntaxes are very useful for partitioned tables,
especially for batch job.
Therefore, I propose to support the following statement about partitioned table:
{code:sql}
-- add partition
ALTER TABLE table_name ADD [IF NOT EXISTS] { PARTITION <partition_spec>
[PARTITION <partition_spec> ...] }
-- drop partition
ALTER TABLE table_name DROP [ IF EXISTS ] { PARTITION <partition_spec>
[PARTITION <partition_spec> ...] }
-- rename partition
ALTER TABLE table_name PARTITION <partition_spec> RENAME TO PARTITION
<partition_spec>;
-- show partitions
SHOW PARTITIONS table_name [PARTITION <partition_spec>]
<partition_spec>::
(partition_col_name=partition_col_val, ...)
{code}
was:
This is an umbrella issue which is used to discuss the syntax enhancement about
partitioned table. These new syntaxes are very useful for partitioned tables,
especially for batch job.
Therefore, I propose to support the following statement about partitioned table:
{code:java}
ALTER TABLE table_name { ADD { <schema_component> | (<schema_component> [,
...]) } | MODIFY { <schema_component> | (<schema_component> [, ...]) } | DROP
{column_name | (column_name, column_name, ....) | PRIMARY KEY | CONSTRAINT
constraint_name | WATERMARK} | RENAME old_column_name TO new_column_name |
RENAME TO new_table_name | SET (key1=val1, ...) | RESET (key1, ...) } {code}
> Partitioned table statement enhancement
> ---------------------------------------
>
> Key: FLINK-27237
> URL: https://issues.apache.org/jira/browse/FLINK-27237
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Reporter: dalongliu
> Priority: Major
> Fix For: 1.16.0
>
>
> This is an umbrella issue which is used to discuss the syntax enhancement
> about partitioned table. These new syntaxes are very useful for partitioned
> tables, especially for batch job.
> Therefore, I propose to support the following statement about partitioned
> table:
> {code:sql}
> -- add partition
> ALTER TABLE table_name ADD [IF NOT EXISTS] { PARTITION <partition_spec>
> [PARTITION <partition_spec> ...] }
> -- drop partition
> ALTER TABLE table_name DROP [ IF EXISTS ] { PARTITION <partition_spec>
> [PARTITION <partition_spec> ...] }
> -- rename partition
> ALTER TABLE table_name PARTITION <partition_spec> RENAME TO PARTITION
> <partition_spec>;
> -- show partitions
> SHOW PARTITIONS table_name [PARTITION <partition_spec>]
> <partition_spec>::
> (partition_col_name=partition_col_val, ...)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
