Standardize naming of PipelineResult objects
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
Today:
PipelineResult is an interface returned by running a pipeline.
DataflowPipelineJob is the Dataflow implementation of that interface
FlinkRunnerResult is the Flink implementation
EvaluationContext is the Spark implementation
DirectPipelineResult is the DirectRunner implementation
Ideally, all the names would indicate that they are a PipelineResult, like the DirectRunner does.
Imported from Jira [BEAM-726](https://issues.apache.org/jira/browse/BEAM-726). Original Jira may contain additional context.
Reported by: bchambers.
Contributor guide
Research direction
Locate the declarations and usages of PipelineResult, DataflowPipelineJob, FlinkRunnerResult, EvaluationContext, and DirectPipelineResult across the runner implementations. Compare how each implementation is referenced before deciding consistent names; the work is done when the implementations and their references use standardized PipelineResult-oriented naming.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100