#AI COMMIT# Add Dependabot ignore rules for Flink shims modules#5441
Merged
Conversation
Dependabot has raised PRs (#5426, #5427) that upgrade Flink dependencies from 1.16.2 to 1.20.4 inside flink-shims-1.16.2. This is incorrect because shims modules are version-specific compatibility layers — the module name must match the supported engine version. Upgrading the dependency in-place would break the shims contract and likely cause compilation or runtime failures across 4 major Flink versions. The correct approach to support a newer Flink version is to create a new shims module (e.g. flink-shims-1.20.4) following the existing pattern, rather than modifying the existing flink-shims-1.16.2 module. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
aiceflower
added a commit
to aiceflower/linkis
that referenced
this pull request
Jun 15, 2026
…he#5441) Dependabot has raised PRs (apache#5426, apache#5427) that upgrade Flink dependencies from 1.16.2 to 1.20.4 inside flink-shims-1.16.2. This is incorrect because shims modules are version-specific compatibility layers — the module name must match the supported engine version. Upgrading the dependency in-place would break the shims contract and likely cause compilation or runtime failures across 4 major Flink versions. The correct approach to support a newer Flink version is to create a new shims module (e.g. flink-shims-1.20.4) following the existing pattern, rather than modifying the existing flink-shims-1.16.2 module. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
aiceflower
added a commit
to aiceflower/linkis
that referenced
this pull request
Jun 15, 2026
…he#5441) Dependabot has raised PRs (apache#5426, apache#5427) that upgrade Flink dependencies from 1.16.2 to 1.20.4 inside flink-shims-1.16.2. This is incorrect because shims modules are version-specific compatibility layers — the module name must match the supported engine version. Upgrading the dependency in-place would break the shims contract and likely cause compilation or runtime failures across 4 major Flink versions. The correct approach to support a newer Flink version is to create a new shims module (e.g. flink-shims-1.20.4) following the existing pattern, rather than modifying the existing flink-shims-1.16.2 module. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
aiceflower
added a commit
to WeDataSphere/linkis
that referenced
this pull request
Jun 15, 2026
…he#5441) Dependabot has raised PRs (apache#5426, apache#5427) that upgrade Flink dependencies from 1.16.2 to 1.20.4 inside flink-shims-1.16.2. This is incorrect because shims modules are version-specific compatibility layers — the module name must match the supported engine version. Upgrading the dependency in-place would break the shims contract and likely cause compilation or runtime failures across 4 major Flink versions. The correct approach to support a newer Flink version is to create a new shims module (e.g. flink-shims-1.20.4) following the existing pattern, rather than modifying the existing flink-shims-1.16.2 module. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
aiceflower
added a commit
to WeDataSphere/linkis
that referenced
this pull request
Jun 16, 2026
…he#5441) Dependabot has raised PRs (apache#5426, apache#5427) that upgrade Flink dependencies from 1.16.2 to 1.20.4 inside flink-shims-1.16.2. This is incorrect because shims modules are version-specific compatibility layers — the module name must match the supported engine version. Upgrading the dependency in-place would break the shims contract and likely cause compilation or runtime failures across 4 major Flink versions. The correct approach to support a newer Flink version is to create a new shims module (e.g. flink-shims-1.20.4) following the existing pattern, rather than modifying the existing flink-shims-1.16.2 module. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dependabot has raised PRs (#5426, #5427) that upgrade Flink dependencies from 1.16.2 to 1.20.4 inside flink-shims-1.16.2. This is incorrect because shims modules are version-specific compatibility layers — the module name must match the supported engine version. Upgrading the dependency in-place would break the shims contract and likely cause compilation or runtime failures across 4 major Flink versions.
The correct approach to support a newer Flink version is to create a new shims module (e.g. flink-shims-1.20.4) following the existing pattern, rather than modifying the existing flink-shims-1.16.2 module.
What is the purpose of the change
EngineConn-Core defines the the abstractions and interfaces of the EngineConn core functions.
The Engine Service in Linkis 0.x is refactored, EngineConn will handle the engine connection
and session management.
Related issues/PRs
Related issues: close #590 close #591
Related pr:#591
Brief change log
Checklist