Yes, I agree with your viewpoint. I created an issue[1] to trace it, and I
think we can fix it as soon as possible to start a new rc.
What's more, I believe that our current e2e testing does not cover such
scenarios, which we need to supplement in the future.
For the 3.4 release, I think there sho
Hi Yanquan,
I think you are completely right. This current state doesn't work. So I'm
calling RC2 off until we fix this issue.
We added one code path in 3.4 (!) that made this issue probably more
obvious but the unchecked use of guava has been going on since 2 years. We
have more than 10 instance
I checked:
- Review JIRA release notes
- Verify hashes and verify signatures
- Build success from source with JDK17 & maven3.8.6
- Source code artifacts matching the current release
- Read the announcement blog
- Verify that the major version is 55
I am trying to use the jar flink-sql-connector-k
