[
https://issues.apache.org/jira/browse/FLINK-26079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490729#comment-17490729
]
Piotr Nowojski commented on FLINK-26079:
----------------------------------------
{quote}
The 1st option is resilient to failures because job graph is generated once.
The main disadvantage is multiple places where it has to be checked;
DataSourceTask for example uses TaskConfig instead of StreamConfig IIUC.
{quote}
Why is that so? {{StreamTask#createStateBackend}} or
{{StateBackendLoader#fromApplicationOrConfigOrDefault}} could be that one
place. {{DataSourceTask}} is a legacy DataSet API class. We can safely limit
ourselves just to {{StreamTask}}.
I don't like that we would have to pass the restore mode to implement such
temporary check, but I don't know what's the alternative? Can we actually fix
this properly before the release? As this is a bug, we could fix it after the
feature freeze.
> Disallow combination of Changelog backend with CLAIM restore mode when
> recovering from non-changelog checkpoint
> ---------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-26079
> URL: https://issues.apache.org/jira/browse/FLINK-26079
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Configuration, Runtime / State Backends
> Reporter: Roman Khachatryan
> Assignee: Roman Khachatryan
> Priority: Blocker
> Fix For: 1.15.0
>
>
> Extracted from FLINK-25872.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
