[ 
https://issues.apache.org/jira/browse/FLINK-41454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martijn Visser updated FLINK-41454:
-----------------------------------
    Fix Version/s: jdbc-4.1.1

> JDBC backwards compatibility workflow fails because Flink 2.0 and 2.1 
> SNAPSHOTs are no longer published
> -------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-41454
>                 URL: https://issues.apache.org/jira/browse/FLINK-41454
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / JDBC
>    Affects Versions: jdbc-5.0.0, jdbc-3.5.0, jdbc-4.1.1
>            Reporter: Martijn Visser
>            Assignee: Martijn Visser
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: jdbc-5.0.0, jdbc-4.1.1
>
>
> The "Flink Connector JDBC CI Backwards Compatibility" workflow fails on every 
> run since 2026-11-03, on main as well as on PRs: 
> https://github.com/apache/flink-connector-jdbc/actions/runs/43087647639/job/130756151967
> {code}
> [ERROR] Failed to execute goal on project flink-connector-jdbc-parent: Could 
> not resolve dependencies for project 
> org.apache.flink:flink-connector-jdbc-parent:pom:5.0-SNAPSHOT: The following 
> artifacts could not be resolved: 
> org.apache.flink:flink-connector-base:jar:2.0-SNAPSHOT, ...
> {code}
> 2.0-SNAPSHOT and 2.1-SNAPSHOT are no longer in the Apache snapshot 
> repository. The v3.4 matrix (1.18-SNAPSHOT, 1.19-SNAPSHOT) has the same 
> problem.
> The module was added in FLINK-35370 to test the FLIP-449 package move. Since 
> 4.0 the old packages are gone and the module's tests use the new API, so on 
> main and v4.1 we should remove the module and the workflow, and keep the 
> PostgreSQL JdbcSink tests by moving them to flink-connector-jdbc-postgres. On 
> v3.4 we should switch the matrix to released Flink versions.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to