Re: Flink SQL CDC connector do nothing to the setting "debizum.*" when create the source table

> 2024年10月10日 上午4:34，Yaroslav Tkachenko 写道： > > Hi Ken, > > Snapshotting is implemented differently in Flink CDC, it doesn't re-use > Debezium's implementation. So you can override some Debezium properties using > "debezium.", but not "debezium.snapshot.". Yeah, Yaroslav is right that Flink

Re: Request to joining Apache Flink community on Slack

Welcome Ken, I’ve sent the invitation to your email. Best, Leonard > 2024年10月10日 上午3:52，Ken CHUAN YU 写道： > > Hi there > > I like to join the Apache Flink community on Slack, my mail address for slack > is: ken.h...@vestiairecollective.com >

Re: Flink SQL CDC connector do nothing to the setting "debizum.*" when create the source table

Dear Yaroslav Thanks for the explanation :-) So if I just want partial snapshot base on certain statement is it possible to do you Flink CDC? The reason is the table is huge(100+ GBs) so full snapshot would overwhelm the Flink application. Or are there any other practices that I can follow here ?

Re: Flink SQL CDC connector do nothing to the setting "debizum.*" when create the source table

Hi Ken, Snapshotting is implemented differently in Flink CDC, it doesn't re-use Debezium's implementation. So you can override some Debezium properties using "debezium.", but not "debezium.snapshot.". On Wed, Oct 9, 2024 at 12:46 PM Ken CHUAN YU wrote: > Hi there > I have issue to use flink sql

Request to joining Apache Flink community on Slack

Hi there I like to join the Apache Flink community on Slack, my mail address for slack is: ken.h...@vestiairecollective.com

Flink SQL CDC connector do nothing to the setting "debizum.*" when create the source table

Hi there I have issue to use flink sql connector to capture change data from MariaDB(MySQL) when configure “debezium.* settings here are more details: I have following table in the source database (MariaDB): ‘’’CREATE TABLE `client_test` ( `id` int(11) unsigned NOT NULL AUTO_INCREMENT, `name` varc

Job fails with exception (uncommitted transactions) at stop with savepoint but savepoint is created

Hi, I’m getting an exception at stop-with-savepoint. The savepoint is still created but the job fails. I’d like to know what the implications and consequences of the failure are (having job configured as exactly once) and how can It be avoided. Starting the job with that savepoint looks to wor

Re: Kafka SQL Connector loses data if deserialization error occures

Finally I found that in order to execute many insert statements in one job I need to use STATEMENT SET. This solved the problem. ср, 9 окт. 2024 г. в 12:17, Ilya Karpov : > During this morning debug I've found that if I comment one of two insert > expressions and submit sql, then only one job wil

Re: Kafka SQL Connector loses data if deserialization error occures

During this morning debug I've found that if I comment one of two insert expressions and submit sql, then only one job will be created in the flink cluster. If a corrupted message causes failure of this job then flink behaves correctly: checkpoint does not happen, offset is not committed! Modified