GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/2714
[FLINK-4935] [webfrontend] Submit job with savepoint
This builds on top of #2712 and only the last commit 4265834 is relevant.
Allows to submit a job via the REST API and restoring from a savpeoint:
## Changes
- Adds documentation for the REST API `/jars/:jarid/run` command
- Adds two new query parameters to run a JAR with the savepoint restore
settings:
1. `savepointPath`: Sets the savepoint path
2. `ignoreUnmappedState`: Ignores unmapped state (default `false`)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/flink 4935-rest_submit_restore_savepoint
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2714.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 #2714
----
commit dc278c51b2bf1f580a6b4cb1670fb70ac871515f
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 57621d30dfc4360c786d557a1a00fb57e2ade372
Author: Ufuk Celebi <[email protected]>
Date: 2016-10-26T16:05:26Z
[FLINK-4445] [checkpointing] Add option to ignore unmapped checkpoint state
Allows to ignore checkpoint state that cannot be mapped to a job vertex when
restoring.
commit 4265834229c942e17b5eacc3900a93eea9f00c26
Author: Ufuk Celebi <[email protected]>
Date: 2016-10-27T14:26:36Z
[FLINK-4935] [webfrontend] Submit job with savepoint
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
