Changelog Stream Processing with Apache Flink
summary
Apache Flink SQL processes tables as change logs and ships an optimizer that turns streams into Flink SQL as changelog processor semantics: four change kinds (insert, update-before, update-after, delete) flow through operators. Demo uses MySQL with Debezium/Flink CDC versus JDBC snapshot, joins transactions to customers with a time-version lookup join, and shows a upsert optimization that cuts downstream traffic by ~50% when primary keys exist. Table API can export to DataStream and back for custom operators or ML.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:41Who am I
- 1:28What is Apache Flink
- 4:02How Flink works
- 6:01Who is using Flink
- 6:43Flink APIs
- 7:49Data Stream API
- 9:12Table and SQL API
- 12:41Flink SQL
- 13:52Stream Table Duality
- 15:41Stream Table Duality Example
- 17:51Sources
- 19:34Retraction mode
- 24:46Transitions
- 26:11Demo
- 33:58Summary
related talks
42mChange Data Capture and Processing with Flink SQL
27mUnderstanding stream table duality using Kafka, Flink SQL and Debezium format
23mBetter, Faster, Stronger Streaming: Your First Dive into Flink SQL
35mFlink's Table & DataStream API: A Perfect Symbiosis
30mChange Data Capture With Flink SQL And Debezium
39mBetter, Faster, Stronger Streaming: Your First Dive into Flink SQL
43mLeverage the power and simplicity of SQL on Apache Flink
23mFrom Streams to Tables and Back Again: A Demo of Flink’s Table & SQL API
