The DirectRunner should interact more directly with SplittableDoFn
Open
direct
improvement
P3
runners
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
The runner has the capability to more accurately use the available interactions with SplittableDoFn. It should implement the transform as a primitive rather than using state and timers to emulate one.
Imported from Jira [BEAM-1710](https://issues.apache.org/jira/browse/BEAM-1710). Original Jira may contain additional context.
Reported by: tgroh.
Contributor guide
Research direction
Start by reading the DirectRunner handling for SplittableDoFn and how it currently uses state and timers to emulate the transform. Determine the primitive interaction required and verify that DirectRunner uses it directly without the emulation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100