Timo Theusner created FLINK-41212:
-------------------------------------
Summary: Reject FULL refresh mode from a plain TableEnvironment
Key: FLINK-41212
URL: https://issues.apache.org/jira/browse/FLINK-41212
Project: Flink
Issue Type: Sub-task
Components: Table SQL / Planner
Reporter: Timo Theusner
{{FULL}} tables are refreshed by a {{{}WorkflowScheduler{}}}, which only the
SQL Gateway hosts, so a plain {{TableEnvironment}} cannot schedule them. Reject
creating or converting a table that resolves to {{FULL}} there before any
catalog write, and reject {{{}SUSPEND{}}}, {{RESUME}} and {{DROP}} of existing
{{FULL}} tables with an error naming the SQL Gateway.
Proposed Changes
* Reject in {{DefaultMaterializedTableExecutor}} a create or conversion that
resolves to {{FULL}} without a workflow scheduler, declared or via
{{{}materialized-table.refresh-mode.freshness-threshold{}}}, before any catalog
write
* Reject {{{}SUSPEND{}}}, {{RESUME}} and {{DROP}} of a {{FULL}} table without
a workflow scheduler, naming the SQL Gateway in the error
* Allow {{ALTER}} (catalog only) and {{REFRESH}} (one-off batch job) of a
{{FULL}} table without a workflow scheduler
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
