apache/seatunnel

[Improve][Core] Support for Apache Flink 2.x

Open

#10353 opened on Jan 16, 2026

View on GitHub
 (9 comments) (4 reactions) (1 assignee)Java (6,897 stars) (1,432 forks)batch import
help wanted

Description

Hello,

I would like to propose adding support for Apache Flink 2.0.1 in SeaTunnel.

Background

Apache Flink 2.0 was released on March 24, 2025, and we anticipate that many organizations will consider upgrading to this version. For instance, users may want to leverage new features such as per-topic scan parallelism configuration in Kafka source connectors, which would require a version upgrade.

Proposal

To enable a smooth transition for SeaTunnel users who wish to adopt Flink 2.0, I suggest adding official support for Apache Flink 2.0.1 in SeaTunnel. This would allow users to take advantage of new Flink features without compatibility concerns.

Request

If this aligns with the project's roadmap, would I be able to contribute and develop this feature? I would be happy to submit a pull request for this enhancement.

Thank you for considering this request.

Contributor guide

Tech stack
java
Domain
backenddata
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaApache FlinkSeaTunnel architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The contributor should review the existing Flink runtime module in SeaTunnel (e.g., seatunnel flink starter) to understand the current integration. They need to study Apache Flink 2.0.1 release notes to identify breaking changes and new features. Additionally, it is recommended to check the comments in this issue for any maintainer guidance on preferred implementation approach. The contributor may also look at example Flink 2.x migration guides for other projects.