g>>
Sent: Tuesday, March 26, 2019 2:31
To: dev; user
Subject: [DISCUSS] Remove forceAvro() and forceKryo() from the ExecutionConfig
Hi all!
The ExecutionConfig has some very old settings: forceAvro() and forceKryo(),
which are actually misleadingly named. They cause POJOs to use Avro or Kryo
or
> >> enableForceAvro() and enableForceKryo()? I think if
> >> https://issues.apache.org/jira/browse/FLINK-11917 merged, we could
> >> support to migrate state which was POJO but serialized using Kryo.
> >>
> >> Best
> >> Yun Tang
> >>
-------------
>> *From:* Stephan Ewen
>> *Sent:* Tuesday, March 26, 2019 2:31
>> *To:* dev; user
>> *Subject:* [DISCUSS] Remove forceAvro() and forceKryo() from the
>> ExecutionConfig
>>
>> Hi all!
>>
>> The ExecutionConfig has some very
O but serialized using Kryo.
>
> Best
> Yun Tang
> --
> *From:* Stephan Ewen
> *Sent:* Tuesday, March 26, 2019 2:31
> *To:* dev; user
> *Subject:* [DISCUSS] Remove forceAvro() and forceKryo() from the
> ExecutionConfig
>
> Hi all!
>
> T
6, 2019 2:31
To: dev; user
Subject: [DISCUSS] Remove forceAvro() and forceKryo() from the ExecutionConfig
Hi all!
The ExecutionConfig has some very old settings: forceAvro() and forceKryo(),
which are actually misleadingly named. They cause POJOs to use Avro or Kryo
rather than the POJO serializ
Hi all!
The ExecutionConfig has some very old settings: forceAvro() and
forceKryo(), which are actually misleadingly named. They cause POJOs to use
Avro or Kryo rather than the POJO serializer.
I think we do not have a good case any more to use Avro for POJOs. POJOs
that are also Avro types go th
