-
Notifications
You must be signed in to change notification settings - Fork 141
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
Build for 2.13 #24
Comments
I recall they’ve done it in master, just waiting for the next release which should happen in October. |
Ah cool. Thanks Pierre |
@iravid |
Yeah totally @neko-kai. At the cost of more memory overhead due to 2 additional JVMs running but totally possible. If 2.13 is coming in October though it might be easier to wait for that. |
@iravid new tentative release date is Nov 30. possibly 2.13 is coming soon. Alpakka is already using Kafka 2.4.0-RC1 for there future release. Maybe it would be possible to adopt RC1 too? |
PRs welcome!
…On 28 Nov 2019, 18:37 +0200, Vitalii ***@***.***>, wrote:
@iravid new tentative release date is Nov 30. possibly 2.13 is coming soon.
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=125307901
Alpakka is already using Kafka 2.4.0-RC1 for there future release.
akka/alpakka-kafka#971
Maybe it would be possible to adopt RC1 too?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
We're now building and publishing for 2.13. |
Kafka and Embedded Kafka aren't built for 2.13, so we'll need to think what to do there. Maybe not run tests on 2.13.
This could be a good reason to running Kafka on a separate JVM.
The text was updated successfully, but these errors were encountered: