[
https://issues.apache.org/jira/browse/FLINK-41390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arvid Heise resolved FLINK-41390.
---------------------------------
Fix Version/s: 2.4.0
Resolution: Fixed
Merged into master as e5a4357..dc9bad2.
> Cancel materialized table refresh jobs the catalog could not record
> -------------------------------------------------------------------
>
> Key: FLINK-41390
> URL: https://issues.apache.org/jira/browse/FLINK-41390
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: Timo Theusner
> Assignee: Timo Theusner
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.4.0
>
>
> When a materialized table statement starts a continuous refresh job and the
> catalog then fails to record it, the job keeps running unrecorded. On CREATE
> the job is orphaned. On RESUME, convert-to-MT and the ALTER restart, a retry
> or the ALTER rollback starts a second job writing to the same sink. Cancel
> such jobs, keep the original error when the cleanup fails, and name the
> savepoint when SUSPEND cannot record it.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
