+1 (non-binding)
Best,
Yubin
On Fri, May 24, 2024 at 2:04 PM Rui Fan <1996fan...@gmail.com> wrote:
>
> +1(binding)
>
> Best,
> Rui
>
> On Fri, May 24, 2024 at 1:45 PM Leonard Xu wrote:
>
> > +1
> >
> > Best,
> > Leonard
> >
> > > 2024年5月24日 下午1:27，weijie guo 写道：
> > >
> > > +1(binding)
> > >
>
linweijiang created FLINK-35449:
---
Summary: MySQL CDC Flink SQL column names are case-sensitive
Key: FLINK-35449
URL: https://issues.apache.org/jira/browse/FLINK-35449
Project: Flink
Issue
Hello,
Thanks for opening this discussion Hong.
+1 for the 1.19.1 release and +1 for Hong as release manager. I am happy to
help out, however I will not be back at my laptop until 5th June onwards.
Danny.
On Fri, May 24, 2024 at 1:57 PM Hong Liang wrote:
> Hi all,
>
> I would like to discuss
+1 (binding)
On Tue, May 14, 2024 at 5:26 PM David Radley
wrote:
> Hi Danny,
> Thankyou so much for supporting this flip and for your feedback. I have
> copied your points and responded on the discussion thread here:
> https://lists.apache.org/thread/rmcc67z35ysk0sv2jhz2wq0mwzjorhjb
>
> kind
Hello,
> I am curious what you mean by abused.
I just meant we will end up adding more and more fields to this map over
time, and it may be hard to undo.
> For Apicurio it can be sent at the start of the payload like Confluent
Avro does. Confluent Avro have a magic byte followed by 4 bytes of
Hi Martjin and Alex,
I agree with your summaries, it will be interesting to see what requests there
might be for back ports.
Kind regards, David.
From: Alexander Fedulov
Date: Friday, 24 May 2024 at 14:07
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: [DISCUSS] Proposing an LTS
Hi Danny,
No worries, thanks for replying. I have working prototype code that is being
reviewed. It needs some cleaning up and more complete testing before it is
ready, but will give you the general idea [1][2] to help to assess this
approach.
I am curious what you mean by abused. I guess the
Caican Cai created FLINK-35448:
--
Summary: Translate pod templates documentation into Chinese
Key: FLINK-35448
URL: https://issues.apache.org/jira/browse/FLINK-35448
Project: Flink
Issue Type:
@David
> I agree with Martijn that we only put features into version 2. Back
porting to v1 should not be business as usual for features, only for
security and stability changes.
Yep, this choice is explicitly reflected in the FLIP [1]
@Martijn
> I think our starting point should be "We don't
Hi all,
I would like to discuss creating a new 1.19 patch release (1.19.1). The
last 1.19 release is two months old, and since then, 35 tickets have been
closed [1], of which 7 are blocker/critical [2].
There are 5 items open at the moment; 2 of which are not blocking because
they affect
Hi David,
> If there is a maintainer willing to merge backported features to v1, as
it is important to some part of the community, this should be allowed, as
different parts of the community have different priorities and timelines,
I don't think this is a good idea. Backporting a feature can
Zhongqiang Gong created FLINK-35447:
---
Summary: Flink CDC Document document file had removed but website
can access
Key: FLINK-35447
URL: https://issues.apache.org/jira/browse/FLINK-35447
Project:
Ryan Skraba created FLINK-35446:
---
Summary: FileMergingSnapshotManagerBase throws a
NullPointerException
Key: FLINK-35446
URL: https://issues.apache.org/jira/browse/FLINK-35446
Project: Flink
Ahmed Hamdy created FLINK-35445:
---
Summary: Update Async Sink documentation for Timeout configuration
Key: FLINK-35445
URL: https://issues.apache.org/jira/browse/FLINK-35445
Project: Flink
Hello,
Apologies, I am on vacation and have limited access to email.
I can see the logic here and why you ended up where you did. I can also see
there are other useful metadata fields that we might want to pass through,
which might result in this Map being abused (Kafka Topic, Kinesis Shard,
Hi, zhongqiang.
Thanks for this discussion.
IMO, I agree to update the references in Flink CDC docs from Debezium 1.9
to 2.0 as the Debezium docs in 1.19 have been dropped.
Flink sources in Flink CDC still need to support JDK 1.8. Upgrading
Debezium to version 2.x will be a hard job.
Have you
Hi,
I agree with Martijn that we only put features into version 2. Back porting to
v1 should not be business as usual for features, only for security and
stability changes.
If there is a maintainer willing to merge backported features to v1, as it is
important to some part of the community,
LvYanquan created FLINK-35444:
-
Summary: Paimon Pipeline Connector support changing column names
to lowercase for Hive metastore
Key: FLINK-35444
URL: https://issues.apache.org/jira/browse/FLINK-35444
+1 (binding)
On Fri, May 24, 2024 at 7:31 AM weijie guo
wrote:
> +1(binding)
>
> Thanks for driving this!
>
> Best regards,
>
> Weijie
>
>
> Rui Fan <1996fan...@gmail.com> 于2024年5月24日周五 13:03写道：
>
> > +1(binding)
> >
> > Best,
> > Rui
> >
> > On Fri, May 24, 2024 at 12:01 PM Yanfei Lei wrote:
+1(binding)
Best,
Rui
On Fri, May 24, 2024 at 1:45 PM Leonard Xu wrote:
> +1
>
> Best,
> Leonard
>
> > 2024年5月24日 下午1:27，weijie guo 写道：
> >
> > +1(binding)
> >
> > Best regards,
> >
> > Weijie
> >
> >
> > Lincoln Lee 于2024年5月24日周五 12:20写道：
> >
> >> +1(binding)
> >>
> >> Best,
> >> Lincoln
20 matches
Mail list logo
