Support Display Data on Composite Transforms
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
Today, the Dataflow runner doesn't represent composites all the way to the UI (it reconstructs them from the name). This means it doesn't support attaching Display Data to composites.
With the runner API refactoring, Dataflow runner should start supporting composites, at which point we should make sure that Display Data is plumbed through properly.
Imported from Jira [BEAM-366](https://issues.apache.org/jira/browse/BEAM-366). Original Jira may contain additional context.
Reported by: bchambers.
Contributor guide
Research direction
Start with the Dataflow runner API refactoring and the original Jira issue BEAM-366 to determine how composites are represented and how Display Data reaches the UI. Trace the relevant runner and Display Data entry points, then verify that composites are represented directly and their attached Display Data is preserved through to the UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100