Alibaba Cloud Flink Python Coding

Support VVR 11.8 and newer. For an older job, establish an upgrade target before applying this skill's development or repair guidance.

For every VVR/PyFlink factual answer and API choice, first inspect the selected version's product/API documentation or package source that supports the conclusion. Use model knowledge to guide lookup and reasoning, never as the sole evidence for capabilities, limitations, signatures, or workarounds. Skill references are navigation and product context, not a complete API manual: when they do not cover a question, continue to the linked API documentation or source.

VVR PyFlink and DataFrame

VVR is Alibaba Cloud's managed Flink runtime. Its Python surface includes pyflink.dataframe, introduced in VVR 11.8, alongside Table and DataStream APIs. Community PyFlink knowledge alone misses these VVR capabilities:

• DataFrame: relational transformations, connector I/O, Python UDFs, and bridges to Table/DataStream.
• AI inference: Flink AI Service and built-in LLM operations for prediction, classification, extraction, summarization, and embeddings.
• Multimodal processing: image, audio, and video operations, including decoding, transformation, frame extraction, and model-backed analysis.

Flink sources and sinks connect to external data systems through connectors. DataFrame read_* / write_* methods are convenient Python entry points to them. Use the connector access routes and capability index to choose a dedicated wrapper, a generic connector call, or access to a catalog table prepared in VVP.

DataFrame column expressions reuse pyflink.table.expression.Expression; that API is part of normal DataFrame development.

For new jobs and general API questions, prioritize DataFrame, including its built-in AI and multimodal functions. Use Table/DataStream when explicitly requested or when the target DataFrame API cannot express the required behavior. Preserve the API structure of existing jobs unless migration is requested.