You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Aviem Zur (JIRA)" <ji...@apache.org> on 2017/02/24 07:32:44 UTC

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

     [ https://issues.apache.org/jira/browse/BEAM-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aviem Zur reassigned BEAM-1446:
-------------------------------

    Assignee: Aviem Zur

> Create should take a TypeDescriptor as an alternative to explicitly specifying the Coder
> ----------------------------------------------------------------------------------------
>
>                 Key: BEAM-1446
>                 URL: https://issues.apache.org/jira/browse/BEAM-1446
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Thomas Groh
>            Assignee: Aviem Zur
>            Priority: Minor
>
> {{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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)