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 Tue, 11 Oct 2016 18:54:20 GMT

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

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

I found this issue when using the Direct Runner for a test, which does dynamic re-sharding
as part of the Write transform. It does a GroupByKey -> Values -> Flatten, and Flatten
failed because it did not have an 'IterableLikeCoder' as the input coder, which should be
the case after calling Values form a GBK.

> 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
>




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

Mime
View raw message