Skip to main content

Confluent Cloud Flink Guide

Autopilot scales up and scales down the compute resources that SQL statements use in Confluent Cloud for Apache Flink®. Autopilot assigns resources efficiently to SQL statements submitted in Confluent Cloud and provides elastic autoscaling for the entire time the job is running. One of the biggest benefits of using Confluent Cloud for Apache Flink is the built-in Autopilot capability.

State size​

The state size is the amount of state that a statement has accumulated. Confluent Cloud for Apache Flink enforces a soft limit of 500 GB and hard limit of 1000 GB on the state size for each statement.

Flink SQL Autopilot in Confluent Cloud for Apache Flink | Confluent Documentation

Topic Actions​

Flink Updates: Topic Actions, Terraform support, GCP and Azure Availability

  • Topic Actions, which are pre-packaged, turn-key stream processing workloads that handle common, domain-agnostic requirements. Users only need to provide a minimal amount of basic configuration before submitting an Action, which runs internally on Flink. Actions are designed to be extremely simple to use, allowing users to leverage the power of Flink with just a few clicks. We are starting with support for two common workloads—topic deduplication and field masking—and plan to add more in the future.
    • Transform topic
    • Deduplicate topic
    • Mask fields
    • Create embeddings

Table API, UDFs and Process Table Functions​

From the Flink Table API, UDFs and PTFs demo (2026):

  • Table API for Java is GA: a code-first way to define pipelines (the demo builds a table of high-value transactions above a threshold), with the statement visible in the Flink workspace
  • UDFs are GA: reusable Java or Python logic as an escape hatch when built-ins are not enough. The demo shows Java UDFs on GCP and Python UDFs on AWS (risk-score UDFs created with CREATE FUNCTION and tested with SELECT)
  • Process Table Functions (PTFs) are GA in Java on AWS, Azure and GCP: stateful functions with custom state and timers, for use cases like fraud detection and dynamic pricing. The demo PTF emits a row once a customer has 3 or more transactions inside a time window, showing logic across multiple events where a UDF works per row

Others​