beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1786) AutoService registration of coders, like we do with PipelineRunners
Date Thu, 20 Apr 2017 21:20:04 GMT

    [ https://issues.apache.org/jira/browse/BEAM-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977558#comment-15977558
] 

ASF GitHub Bot commented on BEAM-1786:
--------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/beam/pull/2605


> AutoService registration of coders, like we do with PipelineRunners
> -------------------------------------------------------------------
>
>                 Key: BEAM-1786
>                 URL: https://issues.apache.org/jira/browse/BEAM-1786
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Assignee: Luke Cwik
>             Fix For: First stable release
>
>
> Today, registering coders for auxiliary data types for a library transform is not very
convenient. It the appears in an output/covariant position then it might be possible to use
{{getDefaultOutputCoder}} to solve things. But for writes/contravariant positions this is
not applicable and the library transform must contort itself to avoid requiring the user to
come up with a coder for a type they don't own.
> Probably the best case today is an explicit call to {{LibraryTransform.registerCoders(Pipeline)}}
which is far too manual.
> This could likely be solved quite easily with {{@AutoService}} and a static global coder
registry, as we do with pipeline runners.



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

Mime
View raw message