Have the pipeline supply beam-sdks-java-harness instead of embedding it within the beam-sdks-java-container
Open
harness
improvement
java
P3
portability
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
Have the Java SDK harness container require the user to ship all the dependencies including "beam-sdks-java-harness".
This allows for a bare container where all java code is supplied by the pipeline being run allowing for testing at HEAD.
Imported from Jira [BEAM-3421](https://issues.apache.org/jira/browse/BEAM-3421). Original Jira may contain additional context.
Reported by: lcwik.
Contributor guide
Research direction
Read the original Jira BEAM-3421 for additional context, then locate the Java SDK harness container definition and the pipeline dependency packaging path. Verify how beam-sdks-java-harness is currently embedded; done means the pipeline supplies it and the container can run with Java code supplied by the pipeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devops, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100