Details
-
New Feature
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
None
Description
We already introduced ALTER TABLE statement in FLIP-69 [1], but only support to rename table name and change table options. One useful feature of ALTER TABLE statement is modifying schema. This is also heavily required by integration with data lakes (e.g. iceberg).
Therefore, I propose to support following ALTER TABLE statements (except SET and RENAME TO, others are all new introduced syntax):
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, ...) } <schema_component>:: { <column_component> | <constraint_component> | <watermark_component> } <column_component>:: column_name <column_definition> [FIRST | AFTER column_name] <constraint_component>:: [CONSTRAINT constraint_name] PRIMARY KEY (column_name, ...) NOT ENFORCED <watermark_component>:: WATERMARK FOR rowtime_column_name AS watermark_strategy_expression <column_definition>:: { <physical_column_definition> | <metadata_column_definition> | <computed_column_definition> } [COMMENT column_comment] <physical_column_definition>:: column_type <metadata_column_definition>:: column_type METADATA [ FROM metadata_key ] [ VIRTUAL ] <computed_column_definition>:: AS computed_column_expression
And some examples:
-- add a new column ALTER TABLE mytable ADD new_column STRING COMMENT 'new_column docs'; -- add columns, constraint, and watermark ALTER TABLE mytable ADD ( log_ts STRING COMMENT 'log timestamp string' FIRST, ts AS TO_TIMESTAMP(log_ts) AFTER log_ts, PRIMARY KEY (id) NOT ENFORCED, WATERMARK FOR ts AS ts - INTERVAL '3' SECOND ); -- modify a column type ALTER TABLE prod.db.sample MODIFY measurement double COMMENT 'unit is bytes per second' AFTER `id`; -- modify definition of column log_ts and ts, primary key, watermark. they must exist in table schema ALTER TABLE mytable ADD ( log_ts STRING COMMENT 'log timestamp string' AFTER `id`, -- reoder columns ts AS TO_TIMESTAMP(log_ts) AFTER log_ts, PRIMARY KEY (id) NOT ENFORCED, WATERMARK FOR ts AS ts - INTERVAL '3' SECOND ); -- drop an old column ALTER TABLE prod.db.sample DROP measurement; -- drop columns ALTER TABLE prod.db.sample DROP (col1, col2, col3); -- drop a watermark ALTER TABLE prod.db.sample DROP WATERMARK; -- rename column name ALTER TABLE prod.db.sample RENAME `data` TO payload; -- rename table name ALTER TABLE mytable RENAME TO mytable2; -- set options ALTER TABLE kafka_table SET ( 'scan.startup.mode' = 'specific-offsets', 'scan.startup.specific-offsets' = 'partition:0,offset:42' ); -- reset options ALTER TABLE kafka_table RESET ('scan.startup.mode', 'scan.startup.specific-offsets');
Note: we don't need to introduce new interfaces, because all the alter table operation will be forward to catalog through Catalog#alterTable(tablePath, newTable, ignoreIfNotExists).
[1]: https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/table/sql/alter/#alter-table
[2]: http://iceberg.apache.org/spark-ddl/#alter-table-alter-column
[3]: https://trino.io/docs/current/sql/alter-table.html
[4]: https://dev.mysql.com/doc/refman/8.0/en/alter-table.html
[5]: https://www.postgresql.org/docs/9.1/sql-altertable.html
Attachments
Issue Links
- duplicates
-
FLINK-19062 Improve alter table DDL
- Closed
- is blocked by
-
FLINK-29072 Migrate DDL-related schema handling to the new Schema framework
- Open
- relates to
-
FLINK-17845 Can't remove a table connector property with ALTER TABLE
- Closed
-
FLINK-27237 Partitioned table statement enhancement
- Open
-
FLINK-19062 Improve alter table DDL
- Closed
1.
|
Restrict ALTER TABLE from setting empty table options | In Progress | dalongliu |