This could be a backward-incompatible change, though that notion has many interpretations. What matters is user pain. Technically if we don't break the core SDK, users should be able to use Java SDK >=2.11.0 with KafkaIO 2.11.0 forever.
How are multiple versions of Kafka supported? Are they all in one client, or is there a case for forks like ElasticSearchIO? Kenn On Mon, Apr 1, 2019 at 10:37 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > +1 to remove 0.9 support. > > I think it's more interesting to test and verify Kafka 2.2.0 than 0.9 ;) > > Regards > JB > > On 01/04/2019 19:36, David Morávek wrote: > > Hello, > > > > is there still a reason to keep Kafka 0.9 support? This unfortunately > > adds lot of complexity to KafkaIO implementation. > > > > Kafka 0.9 was released on Nov 2015. > > > > My first shot on removing Kafka 0.9 support would remove second > > consumer, which is used for fetching offsets. > > > > WDYT? Is this support worth keeping? > > > > https://github.com/apache/beam/pull/8186 > > > > D. > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
