-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Task]: Remove Kafka jars from Beam Java SDK Container #25070
Comments
lukecwik
added a commit
to lukecwik/incubator-beam
that referenced
this issue
Jan 18, 2023
This was added as a temporary work-around when the XLang expansion service did not support returning additional dependencies. This removes that dependency prevent conflicts and allowing the user to control which Kafka dependency version they want to use. Fixes apache#25070
3 tasks
lukecwik
added a commit
that referenced
this issue
Jan 19, 2023
This was added as a temporary work-around when the XLang expansion service did not support returning additional dependencies. This removes that dependency prevent conflicts and allowing the user to control which Kafka dependency version they want to use. For #25070
lukecwik
added a commit
to lukecwik/incubator-beam
that referenced
this issue
Jan 19, 2023
…#25072) This was added as a temporary work-around when the XLang expansion service did not support returning additional dependencies. This removes that dependency prevent conflicts and allowing the user to control which Kafka dependency version they want to use. For apache#25070
3 tasks
johnjcasey
pushed a commit
that referenced
this issue
Jan 19, 2023
) This was added as a temporary work-around when the XLang expansion service did not support returning additional dependencies. This removes that dependency prevent conflicts and allowing the user to control which Kafka dependency version they want to use. For #25070
Merged into 2.45.0 release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What needs to happen?
This was added as a temporary work-around when the XLang expansion service did not support returning additional dependencies. This removes that dependency prevent conflicts and allowing the user to control which Kafka dependency version they want to use.
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: