Skip to content

[FLINK-41129][release] Add release notes for Flink 2.4 - #29957

Draft
RocMarshal wants to merge 1 commit into
apache:release-2.4from
RocMarshal:FLINK-41129.2.4
Draft

RocMarshal wants to merge 1 commit into
apache:release-2.4from
RocMarshal:FLINK-41129.2.4

Conversation

@RocMarshal

Copy link
Copy Markdown
Contributor

What is the purpose of the change

Release note for 2.4.

After reviewed, the missing zh edition context parts would be supplemented.

Brief change log

(for example:)

  • The TaskInfo is stored in the blob store on job creation time as a persistent artifact
  • Deployments RPC transmits only the blob storage reference
  • TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change

Please make sure both new and modified tests in this PR follow the conventions for tests defined in our code quality guide.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

  • Added integration tests for end-to-end deployment with large payloads (100MB)
  • Extended integration test for recovery after master (JobManager) failure
  • Added test that validates that TaskInfo is transferred only once across recoveries
  • Manually verified the change by running a 4 node cluster with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (yes / no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
  • The serializers: (yes / no / don't know)
  • The runtime per-record code paths (performance sensitive): (yes / no / don't know)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
  • The S3 file system connector: (yes / no / don't know)

Documentation

  • Does this pull request introduce a new feature? (yes / no)
  • If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

Generated-by: [Tool Name and Version]

@flinkbot

flinkbot commented Nov 15, 2026 •

Copy link
Copy Markdown
Collaborator

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

@och5351 och5351 left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I compared the document [1] with the PR [2] and confirmed that the relevant changes are properly reflected.
LGTM.

[1] Flink 2.4 Release
[2] 2.3 Release

@weiqingy weiqingy left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for writing this. I checked it against the release-2.4 branch and left a few questions inline.


# Release notes - Flink 2.4

These release notes discuss important aspects, such as configuration, behavior or dependencies,

@weiqingy weiqingy Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Flink 2.4 moves from SLF4J 1.7 to SLF4J 2.0 (FLINK-40574). Users who still use Logback 1.2, or who bundle slf4j-api 1.x in their jars, may get no logs after upgrading. Flink 2.4 also stops reading some old config keys, such as kubernetes.container.image, yarn.ship-directories and akka.client.timeout (FLINK-40734). Should we mention both here, so users know before they upgrade?

starting a Flink cluster. Tests can configure scalar and table arguments, partitioning, and
initial state, feed rows into individual inputs, and inspect the resulting output.

The harness also supports advancing watermarks and the system clock, inspecting timers,

@weiqingy weiqingy Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the 2.4 test harness does not support the system clock, state TTL, or changelog handling yet. The PTF docs (ptfs.md) list TTL as not supported, and changelog support is planned for 2.5 (FLINK-40577). Could we remove those three from this sentence?

table without dropping and recreating the catalog object. The conversion preserves the table's
identity and underlying storage and starts a refresh job for the defining query.

Conversion is disabled by default. Enable it when initializing the session with:

@weiqingy weiqingy Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think SET works for this option. Flink reads it only when the session starts, for example from config.yaml, so a later SET statement has no effect. Could we tell users to put it in config.yaml instead?

);
```

The catalog is provided by `flink-state-processing-api`. Snapshot metadata views additionally

@weiqingy weiqingy Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the Maven artifact is flink-state-processor-api. flink-state-processing-api is only the folder name in the repo. The jar is also in the opt/ folder of the distribution, not lib/, so users need to add it to the classpath first. Should we say that here?

@RocMarshal RocMarshal mentioned this pull request Nov 20, 2026
1 task done
@github-actions github-actions Bot added the community-reviewed PR has been reviewed by the community. label Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-reviewed PR has been reviewed by the community. target:release-2.4

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants