Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
1.11.0
-
None
-
None
Description
If I resume a job from a savepoint which is modified by state processor API, such as loading from /savepoint-path-old and writing to /savepoint-path-new, the job resumed with savepointpath = /savepoint-path-new while throwing an Exception :
/savepoint-path-new/{some-ui-id} (No such file or directory).
I think it's an issue because of flink 1.11 use absolute path in savepoint and checkpoint, but state processor API missed this.
The job will work well with new savepoint(which path is /savepoint-path-new) if I copy all dictionary except `_metadata from` /savepoint-path-old to /savepoint-path-new.
Attachments
Issue Links
- is broken by
-
FLINK-5763 Make savepoints self-contained and relocatable
- Closed
- requires
-
FLINK-14942 State Processing API: add an option to make deep copy
- Closed