Hi Stefan,
Thank you for analyzing the issue and providing a quick
reply. We are looking to go ahead with the programmatic method of rewriting
the metadata with the new path. We were successfully able to de-serialize
and serialize the metadata to a new path, but still we see that
Hi,
the first case sounds like you made a mistake when editing the paths manually
and deleted one ore more bytes that were not part of the path and thus
corrupted the meta data. For the second approach, of course you also need to
replace the paths after reading and before rewriting the
Small correction, on the first case: more likely is that you changed the path
string but I think those are prefixed by the string length, so that would
require manual adjustment as well to not corrupt the metadata.
> On 11. Apr 2019, at 14:42, Stefan Richter wrote:
>
> Hi,
>
> the first case
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
wrote:
> Hi All,
>We are trying to restore a job using relocated savepoint
> files. As pointed out in the FAQs of
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
