@eliaslevy ok now I get your point, sorry for confusion. In that case my objection is mostly invalid, since we should be able to use the latest kafka client (for example 2.0) to talk with all the previous versions. I expect that the latest version should be also the most stable one.
@yanghua in the option proposed by @eliaslevy we would only be using one version (the latest) of the kafka client, thus there would be no special cases. In this scenario, when we are upgrading from `0.11` to `1.0`, effectively we would drop `0.11` connector code, replacing it with `1.0` code. Generally speaking I would be in favour of such option. However there would be two questions needing an answer: 1. after upgrading our connector from `0.11` to `1.0`, do we keep old `flink-connector-kafka-0.11` module with small tiny proxy classes redirecting to `flink-connector-kafka-1.0` to provide painless migration? 2. what about testing? Should we still test `flink-connector-kafka-1.0` against `0.11` brokers? [ Full content available at: https://github.com/apache/flink/pull/6577 ] This message was relayed via gitbox.apache.org for [email protected]
