Hi Parth, I've pulled Stefan into the conversation who might be able to help you with your problem.
Cheers, Till On Wed, Apr 10, 2019 at 7:17 PM Parth Sarathy <parth.sara...@microfocus.com> wrote: > Hi All, > We are trying to restore a job using relocated savepoint > files. As pointed out in the FAQs of savepoint documentation, savepoints > have absolute paths recorded in them and hence a simple relocation to > restore the job would fail. As directed in the documentation we tried out > the simple way to refactor the paths by editing them manually, but the job > submission failed with an IllegalStateException as noted below : > Caused by: java.lang.IllegalStateException: Reading invalid > OperatorStateHandle, type: 50 > at > > org.apache.flink.runtime.checkpoint.savepoint.SavepointV2Serializer.deserializeOperatorStateHandle(SavepointV2Serializer.java:499) > > We then went ahead and gave a swing at the second prescribed option of > utilizing the SavepointV2Serializer for deserializing and serializing the > metadata file. Even with this approach we observed that the generated > metadata file still referenced the old absolute path. We are in a stuck in > a > predicament as of now. How is it that we can set / change the absolute > paths > present in the metadata file using the prescribed SavepointV2Serializer. > It’d be helpful if you could provide some insight into this. > > Thanks, > Parth Sarathy > > > > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ >