Hi guys,

We have encountered on some issue related with possibility to 
‘disableGenericTypes’ (disabling Kryo for the job). It seems a very nice as 
idea to ensure that nobody introduce some random change which penalize the 
performance of the job.

The issue we have encountered is that Flink’s KafkaSource is storing 
KafkaTopicPartition in the state for offset recovery, which is serialized with 
Kryo.
For sure this feature itself is not penalizing performance, but looks like it 
reduces the usefulness of the possibility to ‘disableGenericTypes’. Also on the 
side of Flink user there is no good tool to add KafkaTopicPartition’s non-Kryo 
type information.

On of the related tickets I have found: 
https://issues.apache.org/jira/browse/FLINK-12031

Do you know any workaround to ‘disableGenericType’ in case of KafkaSources or 
what do you think making some development to address this issue?

Kind Regards
Oleksandr

Reply via email to