payloads should be separated from core data structures, and primitives distinguished from misc. standardized payloads
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
This is partially done, but should be made clearer. ParDoPayload etc should not live in the same place as Pipeline - the latter is much more stable. WriteFilesPayload should really be evicted so it is not mistaken for part of the model.
Imported from Jira [BEAM-3577](https://issues.apache.org/jira/browse/BEAM-3577). Original Jira may contain additional context.
Reported by: kenn.
Subtask of issue #18605
Contributor guide
Research direction
Start by reading the parent issue #18605 and the linked Jira item BEAM-3577 for context. Locate the definitions of ParDoPayload, Pipeline, and WriteFilesPayload, then determine the intended separation between core data structures, primitives, and miscellaneous standardized payloads. Done means the organization is clear and WriteFilesPayload is no longer mistaken for part of the model.
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