Hi,
Thanks for starting the discussion, I already started testing Cassandra
connector on Flink 1.18. The error in the nightly build linked here is a
known issue tracked by FLINK-32353. To fix it, it needs a change in
connector-parent and in the ci utils that are tracked by FLINK-32563.
Best
Hi,
I looked into both connectors, they both are failing at archunit. I tried a
few things but with my limited experience couldn't make much progress.
Don't want to block the release. If anyone knows what needs to be done,
please move forward with the fixes.
Hopefully, shall be able to help more
Hi,
I can look into pulsar and Cassandra fixes. I agree it's archunit issue
based on the build logs.
I don't have much experience with it, but I was able to reproduce it
locally.
I can send out PR's over the weekend. Do we have JIRA's for this? If not I
can create to track.
Thanks
@sh
On Fri,
Hi Danny,
Thanks a lot for starting the discussion on this topic! I know that
Pulsar is failing because of Archunit, which I expect the same issue
to be for Cassandra (I know that Etienne was working on this). Happy
to help.
Best regards,
Martijn
On Thu, Nov 2, 2023 at 9:08 PM Danny Cranmer
Hey all.
Now Flink 1.18 is released we need to do some connector releases for
integration parity. We can use this thread to start the discussions for
each connector release and spawn separate vote threads. Kafka is done [1]
(thanks Gordon) and AWS connectors are in process [2], I appreciate help
