Re: Clarification on checkpoint/savepoint usage with Kafka (and RabbitMQ)

In short it's encouraged to use savepoint because of the following situation: * You start processing data from offset 0 * 2 savepoints created, one with offset 10, another with 20 * This timeframe Kafka has offset 20 since that's the last processed * At offset 30 you realize that data processed bet

RE: [ANNOUNCE] Apache Flink 2.0.0 released

YES Hi, Thanks for response . If you are interested to see the attendee list, I will send it to you . Are you interested ? I’m waiting for your response. Thank you From: Neelesh Salian Sent: Tuesday, March 25, 2025 12:45 PM To: Jark Wu Cc: Jingsong Li ; Yuan Mei ; Leonard Xu ; user...@flink.ap

RE: Skip Restore Incompatibility of Key Serializer for Savepoint

YES I HELPED , HI Thanks for response . If you are interested to see the attendee list, I will send it to you . Are you interested ? I’m waiting for your response. Thank you. From: Gabor Somogyi Sent: Monday, March 17, 2025 11:14 AM To: 李 琳 Cc: user@flink.apache.org Subject: Re: Skip Restore I

RE: [ANNOUNCE] Apache Flink 2.0.0 released

Hi, Thanks for response . If you are interested to see the attendee list, I will send it to you . Are you interested ? I’m waiting for your response. Thank you. From: Yuan Mei Sent: Tuesday, March 25, 2025 8:10 AM To: Leonard Xu Cc: user...@flink.apache.org; dev ; user ; annou...@apache.org Su

Re: [ANNOUNCE] Apache Flink 2.0.0 released

Congratulations! Thanks for the great work! Best, Xuannan > On Mar 25, 2025, at 15:14, Neelesh Salian wrote: > > Congratulations! > > Regards, > Neelesh S. Salian > > > > On Tue, Mar 25, 2025 at 15:50 Jark Wu > wrote: >> Congratulations! And thanks to all who made

Re: Clarification on checkpoint/savepoint usage with Kafka (and RabbitMQ)

Hello, Is there any further clarification or explanation regarding the subject, please? Best regards. Le mer. 19 mars 2025 à 15:02, mejri houssem a écrit : > Hello, > > So if I understand you well, I cannot rely on the kafka broker offset to > achieve at-least-once guarantee. Without checkpoi

unsubscribe

unsubscribe

Re: Flink CDC is failing for MongoDB with Resume of change stream was not possible, as the resume point may no longer be in the oplog error

Hi Sachin, Seems MongoDB CDC is trying to restore from a previous change stream position, which has been removed from oplog collection. The resumeToken data provided (8267DD842E00A22B0229296E04) was created at Friday, March 21, 2025 3:22:22 PM (4 days ago), which may have exceeded the Mongo

unsubscribe

unsubscribe -- Best Regards, *Xavier*

Re: [ANNOUNCE] Apache Flink 2.0.0 released

Congratulations! Best, Jingsong On Tue, Mar 25, 2025 at 10:40 AM Yuan Mei wrote: > > Thanks for driving this & Congrats! > > Best > Yuan > > On Mon, Mar 24, 2025 at 5:38 PM Leonard Xu wrote: >> >> Congratulations! >> >> Thanks Xintong, Jark, Jiangjie and Martijn for the release management and

Re: Flink job jar file runs with java command not with flink cluster

i used flink 1.20.0 and 1.20.1 I will try with 2.0.0 and update >From Vishnu I P On Tue, Mar 25, 2025 at 1:30 PM Vishnu I P wrote: > the purpose of the flink job is to read data from a pulsar topic and put > that into a postgresql db > > From Vishnu I P > > > On Tue, Mar 25, 2025 at 1:27 PM

Re: Flink job jar file runs with java command not with flink cluster

the purpose of the flink job is to read data from a pulsar topic and put that into a postgresql db >From Vishnu I P On Tue, Mar 25, 2025 at 1:27 PM Vishnu I P wrote: > Hello, > > This is my first message to the Flink mailing list. > > I previously had a Flink job jar that worked flawlessly o

Flink job jar file runs with java command not with flink cluster

Hello, This is my first message to the Flink mailing list. I previously had a Flink job jar that worked flawlessly on my old Debian machine about six months ago. Recently, I migrated to a new Debian PC and deployed the same jar file using the same version of Flink. Although the job appears to run

Flink CDC is failing for MongoDB with Resume of change stream was not possible, as the resume point may no longer be in the oplog error

Hi, We are using Flink CDC as our datastream application deployed on AWS KDA. Our MongoDB is deployed on Mongo Atlas. The versions are: Flink : 1.20.0 MongoCDC (flink-connector-mongodb-cdc) : 3.1.1 After the application is running for few days, I get the following error: java.lang.RuntimeExcept

Re: [ANNOUNCE] Apache Flink 2.0.0 released

Congratulations! Regards, Neelesh S. Salian On Tue, Mar 25, 2025 at 15:50 Jark Wu wrote: > Congratulations! And thanks to all who made this release possible! > > Best, > Jark > > On Tue, 25 Mar 2025 at 14:46, Jingsong Li wrote: > >> Congratulations! >> >> Best, >> Jingsong >> >> On Tue, Mar