Hi David, Thanks for testing.
Yes the jars are built from the same sources and same git tag apart from the Flink version. as it was mentioned in jdbc connector RC thread [1] >The complete staging area is available for your review, which includes: >* all artifacts to be deployed to the Maven Central Repository [2] which contains jars for three Flink versions (1.16.x, 1.17.x, 1.18.x) Please let me know whether this answers your question or not [1] https://lists.apache.org/thread/rlk5kp2vxgkmbxmq4wnco885q5vv9rtp [2] https://repository.apache.org/content/repositories/orgapacheflink-1706/ On Wed, Feb 7, 2024 at 12:18 PM David Radley <david_rad...@uk.ibm.com> wrote: > Hi , > I had a question on Flink jdbc connector new release. I notice for the > last release we have > > https://mvnrepository.com/artifact/org.apache.flink/flink-connector-jdbc/3.1.1-1.16 > > https://mvnrepository.com/artifact/org.apache.flink/flink-connector-jdbc/3.1.1-1.17 > It seems that the 2 jars above are identical apart from the manifest. > > I assume for the new Flink JDBC connector, there will be a 1.16 1.17 and > 1.18 versions in Maven central, each level will be compiled against Flink > 1.6.0, 1.17.0 and 1.18.0 ( or would it be 1.16.3 , 1.17.2 and 1.18.1?) > respectively. Either way the 3 jar files should be the same (apart from the > manifest names) as the dependencies on core Flink are forward compatible. > > We are looking to use a JDBC connector that works with Flink 1.18 and > fixes the lookup join filter issue. So we are planning to build against the > latest 3.1 branch code against 1.18.0– unless the connector is released > very soon – and we would pick that up. > > Kind regards, David. > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU > -- Best regards, Sergey
