This video covers setting an idle timeout on a watermark generator when joining data in Apache Flink®. This can be used when you have two streams, one that has frequent updates, and one that has infrequent updates, and you need to join data without waiting for a fresh watermark from the infrequent one.

Try Flink without worrying about the setup or configuration in Confluent Cloud: https://cnfl.io/3SgC0JN

RELATED RESOURCES
► Event Time and Watermarks from Flink 101 Course - https://cnfl.io/3Whia2j
► How To Use Streaming Joins with Apache Flink - https://youtu.be/ChiAXgTuzaA
► Exactly-Once Processing in Apache Flink - https://youtu.be/YEsP9zW1h10

CHAPTERS

00:00 - Intro

00:05 - Why do we need to set an Idle timeout?

02:51 - Idle timeout in action

05:39 - Summary

–

ABOUT CONFLUENT
Confluent is pioneering a fundamentally new category of data infrastructure focused on data in motion. Confluent’s cloud-native offering is the foundational platform for data in motion – designed to be the intelligent connective tissue enabling real-time data, from multiple sources, to constantly stream across the organization. With Confluent, organizations can meet the new business imperative of delivering rich, digital front-end customer experiences and transitioning to sophisticated, real-time, software-driven backend operations. To learn more, please visit www.confluent.io.

#apacheflink #flink #confluent