Agree with JB, showing deprecation is ok, but I think it is worth to support Kafka 0.9.x for some extra time. Users tend to stay in old data stores because migrating these clusters isn't always so easy.
On Tue, Feb 6, 2018 at 3:56 PM, Jean-Baptiste Onofré <[email protected]> wrote: > +1 to flag as deprecated, but I would wait a bit before simply removing it. > > Regards > JB > > On 02/03/2018 01:12 AM, Raghu Angadi wrote: >> Is anyone using Apache Beam with Kafka 0.9.x and older? >> >> I am thinking of deprecating 0.9.x and 0.10.0 in Beam 2.4 and remove support >> in >> 2.5 or later. 0.10.1 and up will be supported. 0.10.1+ includes much better >> timestamp support. >> >> By deprecation I mean KafkaIO would continue to work with an older version at >> runtime, but would not build with it (e.g. `mvn >> -Dkafka.clients.version=0.9.1` >> fails). We can print a deprecation warning at runtime. >> >> [1]: >> https://github.com/apache/kafka/commit/23c69d62a0cabf06c4db8b338f0ca824dc6d81a7 > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
