Timo Theusner created FLINK-41209:
-------------------------------------
Summary: Run and control materialized table refresh jobs from any
TableEnvironment
Key: FLINK-41209
URL: https://issues.apache.org/jira/browse/FLINK-41209
Project: Flink
Issue Type: Sub-task
Reporter: Timo Theusner
Assignee: Timo Theusner
Only the SQL Gateway's {{MaterializedTableManager}} starts and controls refresh
jobs, through Flink's cluster client in {{flink-clients}}, which no table
module depends on. So {{executeSql()}} materialized-table DDL only writes the
catalog and leaves the table {{INITIALIZING}}, while {{SUSPEND}}, {{RESUME}}
and {{REFRESH}} throw {{UnsupportedOperationException}}. Move the logic into a
planner {{MaterializedTableExecutor}}, used by the SQL Gateway and every
{{TableEnvironment}}, which reaches existing refresh jobs through a new
internal {{PipelineExecutor}} extension in {{flink-core}}.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
