Re: [BULK]Re: DisableGenericTypes is not compatible with Kafka

2020-02-06 Thread Aljoscha Krettek
@flink.apache.org Subject: [BULK]Re: DisableGenericTypes is not compatible with Kafka Unfortunately, the fact that the Kafka Sources use Kryo for state serialization is a very early design misstep that we cannot get rid of for now. We will get rid of that when the new source interface lands ([1]) and

Re: [BULK]Re: DisableGenericTypes is not compatible with Kafka

2020-02-05 Thread Oleksandr Nitavskyi
? Thanks Kind Regards Oleksandr From: Aljoscha Krettek Sent: Tuesday, February 4, 2020 2:29 PM To: user@flink.apache.org Subject: [BULK]Re: DisableGenericTypes is not compatible with Kafka Unfortunately, the fact that the Kafka Sources use Kryo for state serialization

Re: DisableGenericTypes is not compatible with Kafka

2020-02-04 Thread Aljoscha Krettek
Unfortunately, the fact that the Kafka Sources use Kryo for state serialization is a very early design misstep that we cannot get rid of for now. We will get rid of that when the new source interface lands ([1]) and when we have a new Kafka Source based on that. As a workaround, we should chan

Re: DisableGenericTypes is not compatible with Kafka

2020-02-01 Thread Guowei Ma
Hi, I think there could be two workaround ways to 'disableGenericType' in case of KafkaSource : 1. adding the TypeInfo annotation [1] to the KafaTopicPartition. 2. using the reflection to call the private method. :) Maybe we could add this TypeInfo annotation to the KafakaConnector. [1] https://c

DisableGenericTypes is not compatible with Kafka

2020-01-30 Thread Oleksandr Nitavskyi
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 Ka