Allow Splittable DoFn itself to be used as the restriction provider.
Open
core
improvement
P3
python
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
Binding the provider to the DoFn class itself at construction time can be limiting, we should add an option to use the DoFn instance itself as the restriction provider.
Imported from Jira [BEAM-11354](https://issues.apache.org/jira/browse/BEAM-11354). Original Jira may contain additional context.
Reported by: robertwb.
Contributor guide
Research direction
No files or tests are named. Start by locating the Splittable DoFn restriction-provider API and its construction path; done means a DoFn instance can optionally serve as its own restriction provider instead of requiring a separately bound provider class.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100