Build and deploy Apache Flink user-defined functions (UDFs) in Java for stream processing over Kafka. Use this skill when users want to create scalar UDFs, user-defined table functions (UDTFs), or process table…
---
name: flink-udf
description: "Build and deploy Apache Flink user-defined functions (UDFs) in Java for stream processing over Kafka. Use this skill when users want to create scalar UDFs, user-defined table functions (UDTFs), or process table functions (PTFs) in Java, deploy them to Confluent Cloud or local Docker environments, and invoke them from Flink SQL or the Table API. Trigger on: Flink UDF, custom Flink function, process table function, PTF, UDTF, Flink user defined, extend Flink SQL, stateful stream processing with Flink. Do NOT trigger for: Kafka Streams UDFs (use kafka-streams-programming skill), general Flink job development without custom functions, CDC streaming data piplines that include Flink (prefer the confluent-cloud-cdc-tableflow skill), Flink connector setup, or Kafka producer/consumer code."
metadata:
version: "1.0.0"
---
# Flink User-Defined Functions (UDFs)
Build and deploy custom functions in Java for Apache Flink to extend SQL and Table API capabilities with custom logic.
## Function Types
Before proceeding, identify which type of function the user needs:
- **Scalar UDF**: Maps input values to a single output value (e.g., custom hash, string manipulation, calculations)
- **User-Defined Table Function (UDTF)**: Maps input to multiple output rows (e.g., split strings, explode arrays)
- **Process Table Function (PTF)**: Advanced stateful processing with N-to-M semantics, managed state, and timers (e.g., windowing, deduplication, state machines)
## Gather Requirements
Ask the user these questions to determine the implementation path (if not already clear from context):
1. **Deployment target**: Confluent Cloud or local Docker?
2. **Infrastructure**: Deploy new infrastructure (Kafka + Flink) or use existing?