Skip to content

Flink 1.18: support Flink 1.18.1 as a production release line #182

Description

@Flanderzz

Objective

Support exactly Apache Flink 1.18.1 on Java 17 as a second production release line, while keeping Flink 2.2.1 as the default with its existing artifact coordinates and coverage. Flink 1.18 remains experimental until the remaining production gates below are demonstrated.

Shipped compatibility checkpoint

PR #198 adds the selectable profile, released per-line dependencies, qualified 1.18 artifacts, planner/operator and lookup adapters, native state compatibility, connector/format selection, isolated dual-line CI and documented test baselines. PR #200 rejects mixed loader/core/extension payloads before container daemons start. Both PRs passed all 47 CI checks before merge. PR #204 supplies the allocator/glibc deployment prerequisite; #206 extends the upstream UDF execution audit.

Both Java suites, both optimized Linux images, and the selected unchanged upstream suites pass. Native-execution contracts classify the audited cases explicitly; passing unclassified tests do not imply acceleration. The 1.18 Paimon acceptance corpus is its own version-specific module plus documented shared compatibility regressions, not the full cross-version 1.20 common corpus.

The optimized Nexmark comparison retains both transposes and the unchanged benchmark shape. All ten measured queries are slower than stock 1.18 (0.28–0.88x), so this checkpoint makes no performance-improvement claim.

Child issues

Support contract and remaining production gates

The tested target is exactly Flink 1.18.1 on Java 17; Java 11 and Flink 1.18.0 are outside this matrix. Use one source tree and released third-party artifacts only. Keep host-unavailable constructs such as Variant and delta join explicitly N/A on 1.18; supported host shapes outside the native whitelist must decline at planning time with a precise reason. Delta acceleration has no admitted 1.18 artifact and is unavailable on that line.

The intended cross-line upgrade direction is 1.18.1 to 2.2 at the same StreamFusion release. That guarantee is not established yet. Before production support is announced, complete the remaining state ownership and rescaling proof, run real canonical-savepoint upgrades for every owned state shape in both parallelism directions, prove reverse-direction rejection, verify Docker and Podman, and validate the dual-line release workflow. Do not infer any of those guarantees from compilation or a loader smoke test.

Keep coverage in docs/operators/, docs/connectors/ and docs/backends/; deployment and release guarantees belong in docs/deployment.md and docs/releasing.md. Close each child when its remaining work ships. No release was published by this compatibility checkpoint.

Verified main evidence

Verified on main 89da01cdad7342c4d825e36eaf4e8dc73bc7af9f: CI and upstream suites both completed successfully, with 47 successful jobs in total. Results were rechecked on September 20, 2026. See the compatibility contract and upstream coverage and execution evidence.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions