It is possible to extract the operator ids from the savepoint. You should also be able to modify them if you know the serialization format.
But all of this requires messing around with binary data (including digging into Flink's serialization and savepoint code), so I'd only do it if it is really necessary. 2018-09-18 14:21 GMT+02:00 Paul Lam <[email protected]>: > Hi Fabian, > > Thanks for your reply! > > It seems like there is a word missing. Did you mean it’s possible to > extract the operator ids from the savepoint? Or modify the ids in the > savepoint? > > Best, > Paul Lam > > > 在 2018年9月18日，20:09，Fabian Hueske <[email protected]> 写道： > > The auto-generated ids are included in the savepoint data. So, it should > be possible to them from the savepoint. > However, AFAIK, there is no tool to do that. You'd need to manually dig > into the serialized data. > > Cheers, Fabian > > 2018-09-18 13:30 GMT+02:00 vino yang <[email protected]>: > >> Hi Paul, >> >> Referring to the Flink official documentation, it seems that this is not >> possible at this time.[1] >> >> Someone has previously discussed the state of the savepoint in the dev >> mailing list. Perhaps this method can meet your needs after implementation. >> [2] >> >> Thanks, vino. >> >> [1]: https://ci.apache.org/projects/flink/flink-docs-release >> -1.6/ops/state/savepoints.html#faq >> [2]: http://apache-flink-mailing-list-archive.1008284.n3.nabble. >> com/Proposal-Utilities-for-reading-transforming-and-creat >> ing-Streaming-savepoints-td23843.html#a23859 >> >> Paul Lam <[email protected]> 于2018年9月18日周二 下午7:11写道： >> >>> Hi, >>> >>> I have a legacy stateful streaming job running in production, whose >>> operator ids are not set and were auto generated by Flink. And now I’m >>> planning to update the code and explicitly set operator ids for the job. >>> >>> Is it possible to keep the states of the job, since the operator ids >>> would change? Thanks a lot! >>> >>> Best, >>> Paul Lam >> >> > >
