Hi Konstantin,
What you could do, is that you write and intermediate job that has the old
ValueState “oldState”
and the new one “newState”, with the new format.
When an element comes in this intermediate job, you check the oldState if it is
empty for that key or not.
If it is null (empty), y
Hi,
Flink supports upgrading of serializers [1] [2] since version 1.3.
You probably need to upgrade to Flink 1.3 before you can use the feature.
Best, Fabian
[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.4/dev/stream/state/custom_serialization.html
[2] https://issues.apache.org/j
Hi Aljoscha,
Thanks for your reply.
Do you have a suggestion how can we workaround it ?
We have a production system running with Flink and it is mandatory to add
one more field in the state.
Maybe some how we can write our own serializer?
Thanks,
Konstantin
--
Sent from: http://apache-flink
Hi,
I'm afraid Flink does currently not support changing the schema of state when
restoring from a savepoint.
Best,
Aljoscha
> On 13. Mar 2018, at 07:36, kla wrote:
>
> Hi guys,
>
> I have the flink streaming job running (1.2.0 version) which has the
> following state:
>
> private transient
Hi guys,
I have the flink streaming job running (1.2.0 version) which has the
following state:
private transient ValueState>> userState;
With following configuration:
final ValueStateDescriptor>> descriptor =
new ValueStateDescriptor<>("userState",
TypeInformation.of(new UserTyp
