bor Somogyi mailto:gabor.g.somo...@gmail.com>>
发送时间: 2025年2月10日 16:48
收件人: 李 琳 mailto:leili...@outlook.com>>
抄送: user@flink.apache.org<mailto:user@flink.apache.org>
mailto:user@flink.apache.org>>
主题: Re: Skip Restore Incompatibility of Key Serializer for Savepoint
Seems
发送时间:* 2025年2月10日 16:48
> *收件人:* 李 琳
> *抄送:* user@flink.apache.org
> *主题:* Re: Skip Restore Incompatibility of Key Serializer for Savepoint
>
> Seems like I was not clear in my previous suggestions.
> `execution.savepoint.ignore-unclaimed-state=true` would help only if
> F
> *发件人:* Gabor Somogyi
> *发送时间:* Saturday, February 8, 2025 4:58:48 PM
> *收件人:* 李 琳
> *抄送:* user@flink.apache.org
> *主题:* Re: Skip Restore Incompatibility of Key Serializer for Savepoint
>
> Hi leilinee,
>
> Since Flink SQL is not supporting
.org
主题: Re: Skip Restore Incompatibility of Key Serializer for Savepoint
Hi leilinee,
Since Flink SQL is not supporting operator uid configuration there are only
hard ways.
State operator uid change + `execution.savepoint.ignore-unclaimed-state=true`
would be the easy way.
Depending on you cons
Hi leilinee,
Since Flink SQL is not supporting operator uid configuration there are only
hard ways.
State operator uid change +
`execution.savepoint.ignore-unclaimed-state=true` would be the easy way.
Depending on you constraints either you use the state processor API and
remove the
operator whic
