Get started: https://cnfl.io/apache-flink-table-api-module-1 | Learn about how Confluent Cloud terminology maps to Apache Flink® in this short video.
The Apache Flink Table API can connect to Confluent Cloud with just a few lines of code. It requires minimal boilerplate and a small set of configuration parameters.
This is possible because the Confluent Plugin does significant work behind the scenes to make things easier.
This includes:
- Setting up catalogs.
- Creating databases.
- Defining tables.
- And more.
However, to understand how much work the plugin does behind the scenes, we must recognize how Confluent Cloud concepts get translated into Apache Flink concepts.
Use the promo code FLINKTABLEAPIJAVA & CONFLUENTDEV1 to get $25 of free Confluent Cloud usage and skip credit card entry: https://cnfl.io/try-cloud-apache-flink-table-api
Promo code details: https://cnfl.io/apache-flink-table-api-promo-code-details
RELATED RESOURCES
► What is the Apache Flink® Table API? - [ADD LINK TO YOUTUBE VIDEO]
► Module Exercise: https://cnfl.io/apache-flink-table-api-exercise-1
► Apache Flink 101 course - https://cnfl.io/4j9Usj7
► Apache Flink SQL course - https://cnfl.io/40ceBfM
CHAPTERS
00:00 - Intro
00:27 - How to create a Table Environment.
01:09 - What is the Flink resource hierarcy?
02:06 - How do Confluent environments map to Flink?
02:54 - How do Kafka clusters map to Flink?
03:20 - How do Kafka topics map to Flink?
04:32 - Why is a compute pool necessary?
05:15 - Closing
