[BEAM-117] Implement the API for Static Display Metadata

• Type: New Feature
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 0.1.0-incubating
• Component/s: sdk-java-core
• Labels: Done
• Assignee: Scott Wegner
• Reporter: Ben Chambers
• Created: 16/Mar/16 17:50
• Updated: 06/Oct/20 21:58
• Resolved: 25/May/16 23:08

Description

As described in the following doc, we would like the SDK to allow associating display metadata with PTransforms.

https://docs.google.com/document/d/11enEB9JwVp6vO0uOYYTMYTGkr3TdNfELwWqoiUg5ZxM/edit?usp=sharing

Issue Links

• links to: GitHub Pull Request #338
• links to: GitHub Pull Request #355
• links to: GitHub Pull Request #375

Sub-Tasks

• Add DisplayData to SDK: Resolved
• Integrate DisplayData into DataflowPipelineRunner: Resolved
• Integrate DisplayData into DirectPipelineRunner: Resolved
• Publish DisplayData from common PTransforms: Resolved
• Publish DisplayData for PipelineOptions: Resolved
• Add English labels for registered display data: Resolved
• Update package name for DisplayData types: Resolved
• Rename DisplayDataMatchers#includes: Resolved
• Improve fluent interface for manipulating DisplayData.Items: Resolved
• Standardize terminology to "display data" in documentation: Resolved
• Use super.populateDisplayData consistently: Resolved
• Remove ClassForDisplay infrastructure class.: Resolved
• Add display data link URLs for sources / sinks: Resolved
• Register DisplayData from anonymous implementation PTransforms: Resolved
• Combine.GroupedValues re-wraps combineFn from Combine.PerKey and loses identity for DisplayData: Resolved
• Exclude TextSource.minBundleSize default value from display data.: Resolved
• Exclude PipelineOptions with @JsonIgnore from display data: Resolved