You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bundling embedded Kafka in the testkit can make it challenging to support new versions of Kafka in Alpakka Kafka as the release cycle lags Apache Kafka. When we included Embedded Kafka on the classpath it can conflict with the core Kafka client dependency and its dependency tree. Embedded Kafka with Schema Registry also relies on Confluent Platform images which typically lags the Apache Kafka release by 1-2 months and doesn't always support the same Scala versions.
Details
Update any remaining tests to use testcontainers instead of Embedded Kafka
Re-factor SerializationSpec to use testcontainers.
The text was updated successfully, but these errors were encountered:
@ennru All that remains for this work is reorganizing docs. #1209 replaces the last of the tests that depend on embedded-kafka (except for docs snippets).
If we decide not to drop it, then I think we should at least isolate the docs snippet tests in another project so they don't interfere with the rest of the tests.
Short description
Bundling embedded Kafka in the testkit can make it challenging to support new versions of Kafka in Alpakka Kafka as the release cycle lags Apache Kafka. When we included Embedded Kafka on the classpath it can conflict with the core Kafka client dependency and its dependency tree. Embedded Kafka with Schema Registry also relies on Confluent Platform images which typically lags the Apache Kafka release by 1-2 months and doesn't always support the same Scala versions.
Details
SerializationSpec
to use testcontainers.The text was updated successfully, but these errors were encountered: