>>>>
> >>>> It has been a month and we are glad to see that we have completed the
> >>>> release of Kafka 3.3.0 targeting 1.19 and 1.20.
> >>>>
> >>>> Considering that Flink 2.0-preview1 has already been released, I would
>
r bump to 2.0-preview1 locally and found
>>>> that the adaptation changes made in the production code based on
>>>> FlinkKafkaProducer Depreciated work were relatively clear and the
>> amount of
>>>> change was not significant. However, the headache was
nd
> >> that the adaptation changes made in the production code based on
> >> FlinkKafkaProducer Depreciated work were relatively clear and the
> amount of
> >> change was not significant. However, the headache was that there were
> many
> >> adjustments neede
to know if there is already work in the community to bump to
> 2.0-preview1. If not, I can help complete this task (but some suggestions
> may be needed for testing the adaptation in the code).
>
>
>
>
>
> > 2024年9月27日 16:23，Arvid Heise 写道：
> >
> > Dear Flink de
help complete this task (but some suggestions
>> may be needed for testing the adaptation in the code).
>>
>>
>>
>>
>>
>>> 2024年9月27日 16:23，Arvid Heise 写道：
>>>
>>> Dear Flink devs,
>>>
>>> I'd like to in
gt; I'd like to initiate three(!) Kafka connector releases. The main reason for
> having three releases is that we have been slacking a bit in keeping up
> with the latest changes.
>
> Here is the summary:
> 1. Release kafka-3.3.0 targeting 1.19 and 1.20 (asap)
> - Incorporates lots
: Kafka connector releases
Hi Arvid,
Thanks for your reply on this.
So we could do a 3.2.1, if we supported Flink 1.18? Is there a compelling
reason to not support 1.18?
I see that Kafka connectors that supported Flink 1.17 and below had 2 to 6 bug
releases. Is there not an expectation that there
bug release for 1.19 also? I
assume 1.20 as the last v1 release would have bug releases.
Thoughts?
Kind regards, David.
From: Arvid Heise
Date: Friday, 27 September 2024 at 11:12
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Kafka connector releases
Hi David,
thank you very much for your
ig switch to make it happen (except with code
> duplication).
> > > >> However, I'm grateful for any ideas to avoid this release.
> > > >>
> > > >> Best,
> > > >>
> > > >> Arvid
> > > >>
> > > >
t;>
> > >> Best,
> > >>
> > >> Arvid
> > >>
> > >> On Fri, Sep 27, 2024 at 11:11 AM David Radley <
> david_rad...@uk.ibm.com>
> > >> wrote:
> > >>
> > >>> Hi Arvid,
> > >>&
ps://mvnrepository.com/artifact/org.apache.flink/flink-connector-kafka/3.2.0-1.19
> >>> . I am wondering why we need the first deliverable. If we need it for
> the
> >>> bug fixes , why not have a 3.2.1?
> >>> I assume that kafka-3.4.0 will not work with previous Flink releas
gt;>> . I am wondering why we need the first deliverable. If we need it for the
>>> bug fixes , why not have a 3.2.1?
>>> I assume that kafka-3.4.0 will not work with previous Flink releases.
>>> Would it be worth have a config switch to enable the lineage in the
&g
ould it be worth have a config switch to enable the lineage in the
> connector so that we could use it with 1.19? We could maybe do a 3.3 if
> this was the case.
>
> WDYT?
>Kind regards, David.
>
>
>
> From: Arvid Heise
> Date: Friday, 27 September 2024 at 09:24
kafka-3.4.0 will not work with previous Flink releases.
> > Would it be worth have a config switch to enable the lineage in the
> > connector so that we could use it with 1.19? We could maybe do a 3.3 if
> > this was the case.
> >
> > WDYT?
> >Kind regards,
case.
WDYT?
Kind regards, David.
From: Arvid Heise
Date: Friday, 27 September 2024 at 09:24
To: dev@flink.apache.org
Subject: [EXTERNAL] Kafka connector releases
Dear Flink devs,
I'd like to initiate three(!) Kafka connector releases. The main reason for
having three releases is th
Dear Flink devs,
I'd like to initiate three(!) Kafka connector releases. The main reason for
having three releases is that we have been slacking a bit in keeping up
with the latest changes.
Here is the summary:
1. Release kafka-3.3.0 targeting 1.19 and 1.20 (asap)
- Incorporates lo
16 matches
Mail list logo
