No problem, glad to hear that it's working now!
With release candidates, we always publish the url for staged artifacts in
the release candidate vote threads so that you can point your code to
compile against those for testing purposes.
Would be great to have your +1 on the vote thread for 3.0.2
Thanks Gordon!
I didn't know the name of the repository
https://repository.apache.org/content/repositories/orgapacheflink-1675/
Additionally something learned.
Yes, with the new version I can add the dependency
"org.apache.flink" % "flink-connector-kafka" % "3.0.2-1.18",
and compile it
Hi Günter,
With Maven you'd list the staged repository holding the RC artifacts as a
repository:
```
test_kafka_rc
Apache Flink Kafka Connector v3.0.2
https://repository.apache.org/content/repositories/orgapacheflink-1675/
```
With SBT, I think the equivalent is
Hi Gordon,
thanks for working on it.
How can I reference the repository for the new artifact. Referencing
3.0.2-18 I get an unresolved dependency error.
Thanks for a hint.
Günter
sbt:flink_essential_swrapper> compile
[info] Updating
[info] Resolved dependencies
[warn]
[warn] Note:
Hi all,
I've cherry-picked FLINK-30400 onto v3.0 branch of flink-connector-kafka.
Treating this thread as justification to start a vote for 3.0.2 RC #1
immediately so we can get out a new release ASAP. Please see the vote
thread here [1].
@guenterh.lists Would you be able to test this
RC and
> built a fat uber jar from quickstart with Flink 1.18.0 for
> flink-streaming-java and flink-clients, and flink-connector-kafka version
> 3.0.1-1.18
> then submitted to local Flink cluster 1.18.0. Things worked as expected and
> the job ran fine.
Hey，@Gordan
I guess things may work as
Hi Gordon,
I'm wondering if this might be a difference between how Maven and
Gradle build their projects, since you've done your validations with
Maven, but Günter uses Gradle.
In the end, the quickest fix would be to backport FLINK-30400 to the
Flink Kafka 3.0 release branch.
Best regards,
Hi,
Need to fix my previous comment in the last reply - it should be totally
fine that the POM files for flink-connector-kafka 3.0.1-1.18 point to an
older version.
For example, in the ongoing flink-connector-opensearch release 1.1.0-1.18,
the POM files also still point to Flink 1.17.1 [1].
If
Hi all,
There seems to be an issue with the connector release scripts used in the
release process that doesn't correctly overwrite the flink.version property
in POMs.
I'll kick off a new release for 3.0.2 shortly to address this. Sorry for
overlooking this during the previous release.
Best,
Hi Danny
thanks for taking a look into it and for the hint.
Your assumption is correct - It compiles when the base connector is
excluded.
In sbt:
"org.apache.flink" % "flink-connector-kafka" % "3.0.1-1.18"
exclude("org.apache.flink", "flink-connector-base"),
Günter
On 23.11.23 14:24,
Hey all,
I believe this is because of FLINK-30400. Looking at the pom I cannot see
any other dependencies that would cause a problem. To workaround this, can
you try to remove that dependency from your build?
org.apache.flink
flink-connector-kafka
3.0.1-1.18
Hi, Gurnterh
It seems a bug for me that 3.0.1-1.18 flink Kafka connector use flink 1.17
dependency which lead to your issue.
I guess we need propose a new release for Kafka connector for fix this issue.
CC: Gordan, Danny, Martijn
Best,
Leonard
> 2023年11月14日 下午6:53，Alexey Novakov via user
Same behaviour and assumption on my side Alexey. Thanks for testing it.
Günter
On 17.11.23 09:40, Alexey Novakov via user wrote:
I would expect *flink-connector-kafka:3.0.1-1.18* pointing to
*org.apache.flink:flink-connector-base:1.18.0* not to *1.17.0*
However, SBT compiles my project ok
I would expect *flink-connector-kafka:3.0.1-1.18* pointing to
*org.apache.flink:flink-connector-base:1.18.0* not to *1.17.0*
However, SBT compiles my project ok using such versioning:
val flinkVersion = "1.18.0"
val flinkVersion17 = "1.17.1"
val flinkDependencies = Seq(
"org.flinkextended" %%
Isn't it expected that it points to 1.17? That version of the Kafka
connector is meant to be compatible with both Flink 1.17 and 1.18, right?
So the older version should be specified so that the consumer can decide
which Flink version to compile against, otherwise the build tool could
silently
Hi Günterh,
It looks like a problem with the Kafka connector release.
https://mvnrepository.com/artifact/org.apache.flink/flink-connector-kafka/3.0.1-1.18
Compile dependencies are still pointing to Flink 1.17.
Release person is already contacted about this or will be contacted soon.
Best
Hello
I'm getting a dependency error when using the latest Kafka connector in
a Scala project.
Using the 1.17.1 Kafka connector compilation is ok.
With
"org.apache.flink" % "flink-connector-kafka" % "3.0.1-1.18"
I get
[error] (update) sbt.librarymanagement.ResolveException: Error
17 matches
Mail list logo
