Backported to 1.19 and 1.20 so we're fine here.
@Ferenc, thanks for the backportsð
BR,
G
On Wed, Apr 2, 2025 at 8:08â¯PM Gabor Somogyi
wrote:
> Yeah, exactly. Go ahead and ping me, we'll punt it in...
>
> On Wed, Apr 2, 2025 at 7:17â¯PM Ferenc Csaky
> wrote:
>
>> AFAIK the standard YAML config
Yeah, new version of Kafka connector is needed to use 2.x.
On Wed, Apr 2, 2025 at 4:56â¯PM Gulan, Jacob
wrote:
> I'm able to use the 2.x line, but I see that the "flink-connector-kafka"
> latest version is still on 3.4.0-1.20 with no 2.0 tag yet. Will I need to
> wait for the 2.x tag to be rele
Yeah, exactly. Go ahead and ping me, we'll punt it in...
On Wed, Apr 2, 2025 at 7:17â¯PM Ferenc Csaky
wrote:
> AFAIK the standard YAML config possibility were introduced in
> Flink 1.19, it just coexisted with the old solution to keep bw
> compatibility in the 1.x line.
>
> If we bp it to 1.20, i
AFAIK the standard YAML config possibility were introduced in
Flink 1.19, it just coexisted with the old solution to keep bw
compatibility in the 1.x line.
If we bp it to 1.20, it's not much overhead to move it over to
1.19 as well I guess.
WDYT?
On Wednesday, April 2nd, 2025 at 17:23, Gabor S
I've double checked it and the mentioned fix must be adopted to at least
1.20
with the is_standard_yaml condition.
On Wed, Apr 2, 2025 at 5:07â¯PM Gabor Somogyi
wrote:
> But as a general saying, if the issue exists on 1.x line then at least
> 1.20 must have this fix.
> Let me check that and act
But as a general saying, if the issue exists on 1.x line then at least 1.20
must have this fix.
Let me check that and act accordingly...
BR,
G
On Wed, Apr 2, 2025 at 5:00â¯PM Gabor Somogyi
wrote:
> Yeah, new version of Kafka connector is needed to use 2.x.
>
>
>
> On Wed, Apr 2, 2025 at 4:56â¯PM
I'm able to use the 2.x line, but I see that the "flink-connector-kafka" latest
version is still on 3.4.0-1.20 with no 2.0 tag yet. Will I need to wait for the
2.x tag to be released?
From: Gabor Somogyi
Sent: Wednesday, April 2, 2025 10:13 AM
To: dev@flink.apac
