Hello! 👋 Is there a known issue with the JDBC connector causing it to be late with the 1.17.0 release? The official docs for the connector refer to a version (

3.0.0-1.17

) that does not seem to exist (see https://mvnrepository.com/artifact/org.apache.flink/flink-connector-jdbc). Same applies to version

1.17.0

of the connector, which is usually the format we use.

There is still an open vote for the 1.17 version of the connector

Ok thanks for the quick reply. I know connectors have a separate release cycle but in previous previous versions they were quickly published along the main version so was windering if I missed something.

Up until 1.16 the connectors were always released together with the Flink release itself. But that’s no longer the case

I'm assuming the

3.0.0-xxx

versions that appeared lately are related to the release cycle now being pretty much independent?

They are indeed. Only OpenSearch and MongoDB are on 1.0.x since they are new

What would be the recommendation going forward for connector versions? Switching to the

3.0.0-xx

ones? We currently define a single Flink version spread across our pom but I'm assumign this is not gonna play well with future connector releases.

Correct, connectors are decoupled. It depends on the connector if they are compatible with multiple Flink versions or not

Alright. Lastly: do you know where we can track/follow the release of connectors? Referring to the open vote mentionned earlier.

Excellent! Thanks for the quick replies, I know this is an avalanche of questions 🙂