+1 to remove these two connectors. It's a lot of baggage in comparison to
the workarounds that still make it possible to use older Kafka clusters.
On Fri, Aug 28, 2020 at 12:06 PM Aljoscha Krettek
wrote:
> Yes, that should be the process. But I'd try it in a testing environment
> before doing it
Yes, that should be the process. But I'd try it in a testing environment
before doing it in the production environment.
Aljoscha
On 27.08.20 11:42, Paul Lam wrote:
Hi,
I think it’s okay, given that we can either migrate to the universal connector
or still use the compatible 0.10/0.11 connect
Hi,
I think it’s okay, given that we can either migrate to the universal connector
or still use the compatible 0.10/0.11 connector of 1.11 release as Chesnay
mentioned when upgrading to 1.12.
IIUC, the migration process to the universal connector would be (please correct
me if I’m wrong):
1. S
@Konstantin: Yes, I'm talking about dropping those modules. We don't
have any special code for supporting Kafka 0.10/0.11 in the "modern"
connector, that comes from the Kafka Consumer/Producer code we're using.
@Paul: The modern Kafka connector works with Kafka brokers as far back
as 0.10, wou
+1 to remove both the 1.10 and 1.11 connectors.
The connectors have not been actively developed for some time. They are
basically just sitting around causing noise by causing test
instabilities and eating CI time.
It would also allow us to really simplify the module structure of the
Kafka con
Hi Aljoscha,
I am assuming you're asking about dropping the
flink-connector-kafka-0.10/0.11 modules, right? Or are you talking about
removing support for Kafka 0.10/0.11 from the universal connector?
I am in favor of removing flink-connector-kafka-0.10/0.11 in the next
release. These modules woul
Hi Aljoscha,
I'm lightly leaning towards keeping the 0.10 connector, for Kafka 0.10 still
has a steady user base in my observation.
But if we drop 0.10 connector, can we ensure the users would be able to
smoothly migrate to 0.11 connector/universal connector?
If I remember correctly, the univ
Hi all,
this thought came up on FLINK-17260 [1] but I think it would be a good
idea in general. The issue reminded us that Kafka didn't have an
idempotent/fault-tolerant Producer before Kafka 0.11.0. By now we have
had the "modern" Kafka connector that roughly follows new Kafka releases
for a
