ExecutionConfig.
Best
Yun Tang
[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/custom_serializers.html
From: Konstantin Knauf
Sent: Tuesday, March 26, 2019 17:37
To: Stephan Ewen
Cc: Yun Tang; dev; user
Subject: Re: [DISCUSS] Remove forceAvro() and
Good point, Konstantin, that makes sense.
On Tue, Mar 26, 2019 at 10:37 AM Konstantin Knauf
wrote:
> Hi Stephan,
>
> I am in favor of renaming forceKryo() instead of removing it, because users
> might plugin their Protobuf/Thrift serializers via Kryo as advertised in
> our documentation [1]. For
Hi Stephan,
I am in favor of renaming forceKryo() instead of removing it, because users
might plugin their Protobuf/Thrift serializers via Kryo as advertised in
our documentation [1]. For this, Kryo needs to be used for POJO types as
well, if I am not mistaken.
Cheers,
Konstantin
[1]
https://ci
Compatibility is really important for checkpointed state.
For that, you can always directly specify GenericTypeInfo or AvroTypeInfo
if you want to continue to treat a type via Kryo or Avro.
Alternatively, once https://issues.apache.org/jira/browse/FLINK-11917 is
implemented, this should happen aut
Hi Stephan
I prefer to remove 'enableForceKryo' since Kryo serializer does not work
out-of-the-box well for schema evolution stories due to its mutable properties,
and our built-in POJO serializer has already supported schema evolution.
On the other hand, what's the backward compatibility plan
