[
https://issues.apache.org/jira/browse/BEAM-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613295#comment-16613295
]
Tomas Roos commented on BEAM-5354:
----------------------------------
I agree that its not necessary but I would love to provide a fix but at this
moment my knowledge is too limited to figure it out. Do you have any hints for
me in order to be able to debug this faster than having a 2-4 minute feedback
loop when developing against dataflow? It would be great if one could have the
direct runner to oppose the same constraints as dataflow, because most examples
are running fine on the direct runner but now when targeting another runner.
In this case sure we could remove it but on the otherhand that would mean that
the debug.Head won't be usable by developers which I find a bit sad since its
very useful!
> Side Inputs seems to be non-working in the sdk-go
> -------------------------------------------------
>
> Key: BEAM-5354
> URL: https://issues.apache.org/jira/browse/BEAM-5354
> Project: Beam
> Issue Type: Bug
> Components: sdk-go
> Reporter: Tomas Roos
> Priority: Major
>
> Running the contains example fails with
>
> {code:java}
> Output i0 for step was not found.
> {code}
> This is because of the call to debug.Head (which internally uses SideInput)
> Removing the following line
> [https://github.com/apache/beam/blob/master/sdks/go/examples/contains/contains.go#L50]
>
> The pipeline executes well.
>
> Executed on id's
>
> go-job-1-1536664417610678545
> vs
> go-job-1-1536664934354466938
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
