-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow kafka-clients 3.9.x with Spring-Kafka 3.3.x #3662
Comments
@bgK Did you try upgrading your application to use |
@sobychacko I'm getting the following error with
The method signature changed from |
Thanks for that report. We will try to address it soon. |
Fixes: spring-projects#3662 Issue: spring-projects#3662 Add compatibility for both Kafka 3.8.0 and 3.9.0+ by handling different method signatures for setConfigProp: - 3.9.0+: setConfigProp(String, Object) - 3.8.0: setConfigProp(String, String) The change uses reflection to detect Kafka version and call appropriate method.
The test artifacts of
kafka-clients
versions 3.7.0 to 3.8.1 include ajunit-platform.properties
file. JUnit only supports a singlejunit-platform.properties
. As a result, the file provided bykafka-clients
can override the application provided file depending on classpath order. This has been fixed in 3.9.0 with KAFKA-17121.In our application the
junit-platform.properties
file enables an extention for creating a test database.When upgrading from Spring-Kafka 3.1.x to 3.3.x,
kafka-clients
was updated and the extension was no longer executed.As a workaround, we downgraded
kafka-clients
to 3.6.2. This seems to work even though it's not documented as supported.It would be nice if Spring-Kafka 3.3.x could support
kafka-clients
version 3.9.0 as a proper fix.The text was updated successfully, but these errors were encountered: