Redesign PipelineResult API
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
Current state:
Jira https://issues.apache.org/jira/browse/BEAM-443 addresses waitUntilFinish() and cancel().
However, there are additional work around PipelineResult:
need clearly defined contract and verification across all runners
need to revisit how to handle metrics/aggregators
need to be able to get logs
Imported from Jira [BEAM-849](https://issues.apache.org/jira/browse/BEAM-849). Original Jira may contain additional context.
Reported by: peihe0@gmail.com.
Contributor guide
Research direction
Start with the linked Jira issues BEAM-849 and BEAM-443 for the original context around PipelineResult, waitUntilFinish(), and cancel(). Then map the PipelineResult contract across all runners and investigate the open questions about metrics, aggregators, and logs. Done means the contract and its verification requirements are clearly defined across runners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100