snuyanzin commented on code in PR #28287: URL: https://github.com/apache/flink/pull/28287#discussion_r3396415081
########## docs/content/docs/sql/materialized-table/statements.md: ########## @@ -260,6 +261,63 @@ The operation updates the materialized table similarly to [ALTER MATERIALIZED TA See [ALTER MATERIALIZED TABLE AS](#as-select_statement-1) for more details. +## Converting a Table to a Materialized Table + +This lets you adopt a materialized table on top of a table that already exists, without dropping and recreating it. + +`CREATE OR ALTER MATERIALIZED TABLE` can convert an existing regular table into a materialized table in place. The catalog object keeps its identity and underlying storage. Its kind becomes materialized table, and its schema, options, query definition, freshness, and refresh mode are taken from the conversion statement, exactly as for a newly created materialized table. After the conversion, a refresh job is launched just as it is for a newly created materialized table. + + Review Comment: any reason for having double empty lines here and in other places? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
