[
https://issues.apache.org/jira/browse/FLINK-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615140#comment-15615140
]
ASF GitHub Bot commented on FLINK-4445:
---------------------------------------
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/2713
[FLINK-4445] Add option to ignore unmapped checkpoint state
Backport of #2712 for `release-1.1`.
Technically, this adds new behaviour to a bugfix release, but the default
behaviour is not changed and multiple users already ran into this. In such a
case, there is no straight forward way to work around this issue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/flink 4445-unmatched_state-backport_1.1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2713.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2713
----
commit d45e13d2f1e9143458b8c45e2c5201196bf70375
Author: Ufuk Celebi <[email protected]>
Date: 2016-10-26T16:00:21Z
[FLINK-4445] [client] Add ignoreUnmappedState flag to CLI
Allow to specify whether a checkpoint restore should ignore
checkpoint state that it cannot map to the program. This is
exposed via the CLI in the run command:
bin/flink run -s <savepointPath> -i ...
Furthermore, the savepoint restore settings are moved out of
the snapshotting settings.
commit 91f677d8906d7ad92a6919b7756011280a20a5f7
Author: Ufuk Celebi <[email protected]>
Date: 2016-10-27T07:49:01Z
[FLINK-4445] [checkpointing] Add option to ignore unmatched savepoint state
Allows to ignore savepoint state that cannot be mapped to a job vertex when
restoring.
----
> Ignore unmatched state when restoring from savepoint
> ----------------------------------------------------
>
> Key: FLINK-4445
> URL: https://issues.apache.org/jira/browse/FLINK-4445
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing
> Affects Versions: 1.1.1
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
>
> When currently submitting a job with a savepoint, we require that all state
> is matched to the new job. Many users have noted that this is overly strict.
> I would like to loosen this and allow savepoints to be restored without
> matching all state.
> The following options come to mind:
> (1) Keep the current behaviour, but add a flag to allow ignoring state when
> restoring, e.g. {{bin/flink -s <savepoint> --ignoreUnmatchedState}}. This
> would be non-API breaking.
> (2) Ignore unmatched state and continue. Additionally add a flag to be strict
> about checking the state, e.g. {{bin/flink -s <savepoint> --strict}}. This
> would be API-breaking as the default behaviour would change. Users might be
> confused by this because there is no straight forward way to notice that
> nothing has been restored.
> I'm not sure what's the best thing here. [~gyfora], [~aljoscha] What do you
> think?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
