Thanks yanquan for kicking off the next major release!
I’d like to add JDBC sink plugin to Flink-CDC-Pipeline and add support for
engines such as mysql and postgresSQL
[1]
https://docs.google.com/document/d/1bgKV9Teq8ktHZOAJ7EKzgSqP11Q4ZT2EM8BndOtDgy0/edit
[2] https://issues.apache.org/jira/browse
I have updated the FLIP [1] (please double-check) and will add my +1 now to
the voting.
Best,
Arvid
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-477+Amazon+SQS+Source+Connector
On Wed, Sep 25, 2024 at 2:21 PM Saurabh Singh
wrote:
> Hi Flink Devs,
>
> Thanks a lot for the valuabl
+1 (binding),
Best,
Arvid
On Tue, Sep 3, 2024 at 12:35 PM Saurabh Singh
wrote:
> Hi Flink Devs,
>
> Gentle Reminder for voting on FLIP-477: Amazon SQS Source Connector [1].
> [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-477
> +Amazon+SQS+Source+Connector
>
> Regards
> Saurabh & A
Dear Flink Community,
We are excited to share some important news with you!
Flink Forward Asia 2024 is coming up with two major events: the first in
Shanghai on November 29-30, and the second in Jakarta on December 5. These
gatherings will focus on the latest developments, future plans, and
pro
Zhongmin Qiao created FLINK-36397:
-
Summary: Using the offset obtained after a query transaction as a
high watermark cannot ensure exactly-once semantics.
Key: FLINK-36397
URL: https://issues.apache.org/jira/brows
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 lots of deprecati
Jacky Lau created FLINK-36399:
-
Summary: cast result is incorrect
Key: FLINK-36399
URL: https://issues.apache.org/jira/browse/FLINK-36399
Project: Flink
Issue Type: Bug
Components: Tabl
Thanks for the work, Arvid!
I'm not sure if there's any incompatibility issue for 3.2 + 1.20. If
they are fully compatible, what about not dropping support for 1.18 in
3.2.1, and we release one more version 3.2.1-1.20? Then we can use
3.3.0 for the new lineage feature in 1.20 and drop support for
Hi David,
thank you very much for your reply.
> Some thoughts on whether we need the 3 deliverables. And whether we could
follow more traditional fixpack numbering:
> I see that there is already a release for 1.19
https://mvnrepository.com/artifact/org.apache.flink/flink-connector-kafka/3.2.0-1.1
Hi Arvid,
Some thoughts on whether we need the 3 deliverables. And whether we could
follow more traditional fixpack numbering:
I see that there is already a release for 1.19
https://mvnrepository.com/artifact/org.apache.flink/flink-connector-kafka/3.2.0-1.19
. I am wondering why we need the firs
JunboWang created FLINK-36398:
-
Summary: Provide tools for users to obtain Schema mapping
Key: FLINK-36398
URL: https://issues.apache.org/jira/browse/FLINK-36398
Project: Flink
Issue Type: Improv
+1 (binding)
Thanks,
Danny
On Fri, Sep 27, 2024 at 8:15 AM Arvid Heise wrote:
> +1 (binding),
>
> Best,
>
> Arvid
>
> On Tue, Sep 3, 2024 at 12:35 PM Saurabh Singh
> wrote:
>
> > Hi Flink Devs,
> >
> > Gentle Reminder for voting on FLIP-477: Amazon SQS Source Connector [1].
> > [1] https://cwi
Thanks Arvid for the volunteering!
+ 1 for all of the three releases and RM candidate.Qingsheng and I would like
to help the 4.0.0-preview which follows the Flink 2.0 preview,
please feel free to ping us if you need any help.
Btw, for other external connectors which highest supported flink ve
13 matches
Mail list logo