beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Martin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-741) Values transform does not use the correct output coder when values is an Iterable<T>
Date Fri, 14 Oct 2016 17:28:20 GMT

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

Andrew Martin commented on BEAM-741:
------------------------------------

[~kenn] I dug into this more today, and found the specific reason for this failure - the inference
process in Beam checks the coder registry, and if it doesn't find any will try to use a fallback
coder provider. If it fails there, only then will it try to obtain the coder from the producing
transform. In Scio we set our own fallback coder provider, so Beam will never end up using
the output coder from the producing transform. So, in Scio we probably need to prefer using
the default output coder of the producing transform, and fall back as a last resort. I will
close this because it is an issue in Scio, not in Beam.

Thanks!

> Values transform does not use the correct output coder when values is an Iterable<T>
> ------------------------------------------------------------------------------------
>
>                 Key: BEAM-741
>                 URL: https://issues.apache.org/jira/browse/BEAM-741
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Andrew Martin
>            Assignee: Davor Bonaci
>             Fix For: Not applicable
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message