[BEAM-1446] Create should take a TypeDescriptor as an alternative to explicitly specifying the Coder

• Type: Improvement
• Status: Resolved
• Priority: P3
• Resolution: Fixed
• Fix Version/s: 0.6.0
• Component/s: sdk-java-core
• Labels: Done
• Assignee: Aviem Zur
• Reporter: Thomas Groh
• Created: 09/Feb/17 17:20
• Updated: 06/Oct/20 21:50
• Resolved: 27/Feb/17 17:44

Description

getDefaultCreateCoder is provided with the Pipeline's CoderRegistry, which enables it to use standard Coder Inference. For the construction of the Default Create Coder, explicitly providing the TypeDescriptor allows it to ask the CoderRegistry directly rather than attempting to reconstruct the TypeDescriptor based on the elements within the Create.

This also makes some coder specifications significantly more terse, as the type signature must be respecified but the entire coder need not be constructed (e.g. KvCoder.of(VarIntCoder.of(), StringUtf8Coder.of()); becomes new TypeDescriptor<KV<Integer, String>>() {};, which is at least somewhat simpler to type out.

Issue Links

• is related to: BEAM-1704 Create.TimestampedValues should take a TypeDescriptor as an alternative to explicitly specifying the Coder
• links to: GitHub Pull Request #2095