Extend the TestSparkRunner with its own TransformTranslator containing test evaluators
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
When we have to test low level features in the Spark runner, requiring access to the `RDDs` or `DStreams`, we have to create a "fake" `PTransform` with a custom evaluators in the core Spark runner.
In order to avoid to pollute the core runner, this should be done in `TestSparkRunner`.
Imported from Jira [BEAM-1051](https://issues.apache.org/jira/browse/BEAM-1051). Original Jira may contain additional context.
Reported by: jbonofre.
Contributor guide
Research direction
Start with TestSparkRunner and the core Spark runner's existing custom evaluator handling. Compare how fake PTransforms and test evaluators are registered for low-level RDD and DStream tests. Done means those test evaluators are provided by TestSparkRunner without polluting the core runner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spark
- Domain
- data, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100