[
https://issues.apache.org/jira/browse/BEAM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572443#comment-15572443
]
Andrew Martin commented on BEAM-741:
------------------------------------
[~kenn] After investigating further, it seems like the coder for the output of
the values transform is not inferred correctly because of what appears to be
some loss of type information in the type descriptor - the output of the
`Values` transform should be of type Iterable<T> but the raw type is just
Object during the inference process, so the default coder provider is used
(which we set in our own code).
I'm part of a team at Spotify developing Scio (https://github.com/spotify/scio)
and we have a work-in-progress branch for beam porting, and it is some tests in
there that fail. I'd like to have a failing test written in the pure beam API
so you can take a look - that being said, is it possible to invoke the
@RunnableOnService tests locally using the direct runner?
> 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)
