I withdraw my concern -- checked on info on the cluster I will eventually
access. It is on 0.8, so I was speaking too soon. Can't speak to rest of
user base.
On Tue, Apr 2, 2019 at 11:03 AM Raghu Angadi wrote:
> Thanks to David Morávek for pointing out possible improvement to KafkaIO
> for dro
Thanks to David Morávek for pointing out possible improvement to KafkaIO
for dropping support for 0.9 since it avoids having a second consumer just
to fetch latest offsets for backlog.
Ideally we should be dropping 0.9 support for next major release, in fact
better to drop versions before 0.10.1 a
We're still using Kafka 0.10 a lot, similar as 0.9 IMO. To expand multiple
versions in KafkaIO is quite complex now, and it confuses users which is
supported / which is not. I would prefer to support Kafka 2.0+ only in the
latest version. For old versions, there're some options:
1). document Kafka-
> How are multiple versions of Kafka supported? Are they all in one client, or
> is there a case for forks like ElasticSearchIO?
They are supported in one client but we have additional “ConsumerSpEL” adapter
which unifies interface difference among different Kafka client versions
(mostly to sup
Hey Augusto,
I haven't used @DefaultCoder, but it could be the problem here.
What if you specify the coder directly for your PCollection? For example:
pCol.setCoder(AvroCoder.of(YourClazz.class));
Thanks,
Max
On 01.04.19 17:52, Augusto Ribeiro wrote:
Hi Max,
I tried to run the job again
